Broadcast signal transmission device, broadcast signal receiving device, broadcast signal transmission method and broadcast signal receiving method

ABSTRACT

An apparatus for transmitting a broadcast signal, includes a processor to generate a content component for a broadcast service, service signaling information including object flow information for an object flow which carries the content component and signaling information for listing broadcast services, the object flow information including format information representing a payload format of an object, and the service signaling information being carried by transport packets; and a transmitter to transmit the broadcast signal including the signaling information, the service signaling information and the content component.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.15/124,290, filed on Sep. 7, 2016, which is the National Phase of PCTInternational Application No. PCT/KR2015/006422, filed on Jun. 24, 2015,which claims priority under 35 U.S.C. 119(e) to U.S. ProvisionalApplication No. 62/017,241, filed on Jun. 25, 2014, all of which arehereby expressly incorporated by reference into the present application.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to a broadcast signal transmission device,a broadcast signal reception device, and a method of transmitting andreceiving a broadcast signal.

Discussion of the Related Art

In recent digital broadcasting, a method of synchronizing service andcontent transmission is required to support hybrid broadcast enablingreception of audio/video (A/V) over a terrestrial broadcast network andreception of enhancement data over an Internet communication network.

In particular, an application to be used in a future DTV serviceincludes a hybrid broadcast service using a combination of a terrestrialbroadcast network and an Internet communication network. The hybridbroadcast service transmits some broadcast content or enhancement dataassociated with broadcast content, which is transmitted over theterrestrial broadcast network, in real time over the Internetcommunication network, thereby enabling a user to experience a varietyof content. Accordingly, there is a need for broadcast transmission andreception devices for transmitting and receiving broadcast content overthe terrestrial broadcast network and an Internet communication network.

SUMMARY OF THE INVENTION

That is, a digital broadcast system can provide HD (high definition)images, multi-channel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast. In addition, signaling information for receiving adigital broadcast signal needs to be received through various paths.

A broadcast transmission device according to an embodiment of thepresent invention may include a controller for inserting information forproviding a broadcast service into a service signaling message andpacketizing the service signaling message into a transport protocolpacket and a transmission unit for transmitting the transport protocolpacket.

The information for providing the broadcast service may include at leastone of first service information for a timebase including metadata on atimeline which is a series of time information for content, secondservice information of detailed information for acquisition of segmentsconfiguring content in adaptive media streaming, third serviceinformation of a path for acquiring component data configuring contentin the broadcast service, fourth service information for a signalingmessage for an application used in the broadcast service, and fifthservice information for a flow including the component data configuringthe broadcast service.

At least one of the first service information, the second serviceinformation, the third service information and the fourth serviceinformation may include information on a transport mode and bootstrapinformation.

The bootstrap information may include at least one of IP addressinformation capable of acquiring service information based on theinformation on the transport mode, port number information, transportsession identifier information and associated packet identifierinformation.

The fifth service information may include information on a format of atleast one object included in the flow.

The fifth service information may include information indicating whetherpayload included in the at least one object includes component data usedas a default.

The information for providing the broadcast service may includeinformation on a transport session.

The information on the transport session may include information atleast one payload and information on a transport protocol of eachpayload.

The information on the transport session may include at least onepayload and information on a transport protocol of the payload includedin the transport session is included in a transport session level.

A broadcast reception device according to an embodiment of the presentinvention includes a reception unit for receiving a transport protocolpacket including a service signaling message for signaling a broadcastservice, and a controller for extracting the service signaling messagefrom the received transport protocol packet and acquiring informationfor providing a broadcast service from the extracted service signalingmessage.

The information for providing the broadcast service may include at leastone of first service information for a timebase including metadata on atimeline which is a series of time information for content, secondservice information of detailed information for acquisition of segmentsconfiguring content in adaptive media streaming, third serviceinformation of a path for acquiring component data configuring contentin the broadcast service, fourth service information for a signalingmessage for an application used in the broadcast service, and fifthservice information for a flow including the component data configuringthe broadcast service.

At least one of the first service information, the second serviceinformation, the third service information and the fourth serviceinformation may include information on a transport mode and bootstrapinformation.

The bootstrap information may include at least one of IP addressinformation capable of acquiring service information based on theinformation on the transport mode, port number information, transportsession identifier information and associated packet identifierinformation.

The fifth service information may include information on a format of atleast one object included in the flow.

The fifth service information may include information indicating whetherpayload included in the at least one object includes component data usedas a default.

The information for providing the broadcast service may includeinformation on a transport session.

The information on the transport session may include information atleast one payload and information on a transport protocol of eachpayload.

The information on the transport session may include at least onepayload and information on a transport protocol of the payload includedin the transport session is included in a transport session level.

A broadcast transmission method according to an embodiment of thepresent invention includes inserting information for providing abroadcast service into a service signaling message, packetizing theservice signaling message into a transport protocol packet, andtransmitting the transport protocol packet.

A broadcast reception method according to an embodiment of the presentinvention includes receiving a transport protocol packet including aservice signaling message for signaling a broadcast service, extractingthe service signaling message from the received transport protocolpacket, and acquiring information for providing a broadcast service fromthe extracted service signaling message.

According to the embodiment of the present invention, it is possible toincrease transmission efficiency of a broadcast system.

According to the embodiment of the present invention, it is possible toprovide a hybrid broadcast service.

According to the embodiment of the present invention, a broadcastreception device can receive a media stream over broadband.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention;

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention;

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention;

FIG. 4 illustrates a BICM block according to an embodiment of thepresent invention;

FIG. 5 illustrates a BICM block according to another embodiment of thepresent invention;

FIG. 6 illustrates a frame building block according to one embodiment ofthe present invention;

FIG. 7 illustrates an OFDM generation block according to an embodimentof the present invention;

FIG. 8 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention;

FIG. 9 illustrates a frame structure according to an embodiment of thepresent invention;

FIG. 10 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention;

FIG. 11 illustrates preamble signaling data according to an embodimentof the present invention;

FIG. 12 illustrates PLS1 data according to an embodiment of the presentinvention;

FIG. 13 illustrates PLS2 data according to an embodiment of the presentinvention;

FIG. 14 illustrates PLS2 data according to another embodiment of thepresent invention;

FIG. 15 illustrates a logical structure of a frame according to anembodiment of the present invention;

FIG. 16 illustrates PLS mapping according to an embodiment of thepresent invention;

FIG. 17 illustrates EAC mapping according to an embodiment of thepresent invention;

FIG. 18 illustrates FIC mapping according to an embodiment of thepresent invention;

FIG. 19 illustrates an FEC structure according to an embodiment of thepresent invention;

FIG. 20 illustrates a time interleaving according to an embodiment ofthe present invention;

FIG. 21 illustrates the basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention;

FIG. 22 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention;

FIG. 23 illustrates a diagonal-wise reading pattern of a twistedrow-column block interleaver according to an embodiment of the presentinvention;

FIG. 24 illustrates interleaved XFECBLOCKs from each interleaving arrayaccording to an embodiment of the present invention;

FIG. 25 is a diagram showing a protocol stack supporting a broadcastservice according to one embodiment of the present invention;

FIG. 26 is a diagram showing a transport layer of a broadcast serviceaccording to one embodiment of the present invention;

FIG. 27 is a diagram showing the configuration of a media contenttransmission and reception system via an IP network according to oneembodiment of the present invention;

FIG. 28 is a diagram showing the structure of a media presentationdescription (MPD) according to one embodiment of the present invention;

FIG. 29 is a diagram showing the configuration of a broadcast receptiondevice according to one embodiment of the present invention;

FIGS. 30 to 31 are diagrams showing the configuration of a broadcastreception device according to another embodiment of the presentinvention;

FIG. 32 is a diagram showing the configuration of a broadcast receptiondevice according to another embodiment of the present invention;

FIG. 33 is a diagram showing a broadcast transport frame according toone embodiment of the present invention;

FIG. 34 is a diagram showing a broadcast transport frame according toanother embodiment of the present invention;

FIG. 35 is a diagram showing the configuration of a transport packetaccording to one embodiment of the present invention;

FIG. 36 is a diagram showing the configuration of a service signalingmessage according to one embodiment of the present invention;

FIG. 37 is a diagram showing the configuration of a service signalingmessage according to one embodiment of the present invention;

FIG. 38 is a diagram showing the configuration of a broadcast servicesignaling message in a next generation broadcast system according to oneembodiment of the present invention;

FIG. 39 is a diagram showing the meaning of the value of atimebase_transport_mode field and a signaling_transport_mode field in aservice signaling message according to one embodiment of the presentinvention;

FIGS. 40 to 46 are diagrams showing the syntax of a bootstrap( ) fieldaccording to the values of the timebase_transport_mode field and thesignaling_transport_mode field in one embodiment of the presentinvention;

FIG. 47 is a diagram showing a process of acquiring a timebase and aservice signaling message in the embodiments of FIGS. 38 to 46;

FIG. 48 is a diagram showing the configuration of a broadcast servicesignaling message in a next generation broadcast system according to oneembodiment of the present invention;

FIG. 49 is a diagram showing the configuration of a broadcast servicesignaling message in a next generation broadcast system according to oneembodiment of the present invention;

FIG. 50 is a diagram showing the meaning of the value of each transportmode described in FIG. 49;

FIG. 51 is a diagram showing the configuration of a signaling messagefor signaling a component data acquisition path of a broadcast servicein a next generation broadcast system;

FIG. 52 is a diagram showing the syntax of an app_delevery_info( ) fieldaccording to one embodiment of the present invention;

FIG. 53 is a diagram showing the syntax of an app_delevery_info( ) fieldaccording to another embodiment of the present invention;

FIG. 54 is a diagram showing component location signaling including pathinformation capable of acquiring one or more component data configuringa broadcast service;

FIG. 55 is a diagram showing the configuration of the component locationsignaling of FIG. 54;

FIG. 56 is a diagram showing other information included in signaling ofa broadcast service in a next generation broadcast system in oneembodiment of the present invention;

FIG. 57 is a diagram showing a transport mode included in servicesignaling of a next generation broadcast system according to oneembodiment of the present invention;

FIG. 58 is a diagram showing information on a bootstrap included inservice signaling of a next generation broadcast system according to oneembodiment of the present invention;

FIG. 59 is a diagram showing other information included in signaling foran object flow;

FIG. 60 is a diagram showing a combination of information forrepresenting a file template in one embodiment of the present invention;

FIG. 61 is a diagram showing an object flow included in servicesignaling according to one embodiment of the present invention;

FIG. 62 is a diagram showing other information included in signaling ofa broadcast service in a next generation broadcast system in oneembodiment of the present invention;

FIG. 63 is a diagram showing signaling information for transport sessioninformation of a session level according to one embodiment of thepresent invention;

FIG. 64 is a diagram showing signaling information for transport sessioninformation of a session level according to another embodiment of thepresent invention;

FIG. 65 is a flowchart illustrating a process of operating a broadcastreception device according to one embodiment of the present invention;and

FIG. 66 is a flowchart illustrating a process of operating a broadcasttransmission device according to one embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although most terms used in the present invention have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant and their meanings are explainedin detail in the following description as needed. Thus, the presentinvention should be understood based upon the intended meanings of theterms rather than their simple names or meanings.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc. The present invention may process broadcast signalsfor the future broadcast services through non-MIMO (Multiple InputMultiple Output) or MIMO according to one embodiment. A non-MIMO schemeaccording to an embodiment of the present invention may include a MISO(Multiple Input Single Output) scheme, a SISO (Single Input SingleOutput) scheme, etc.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas. The present invention may defines three physical layer(PL) profiles—base, handheld and advanced profiles—each optimized tominimize receiver complexity while attaining the performance requiredfor a particular use case. The physical layer (PHY) profiles are subsetsof all configurations that a corresponding receiver should implement.

The three PHY profiles share most of the functional blocks but differslightly in specific blocks and/or parameters. Additional PHY profilescan be defined in the future. For the system evolution, future profilescan also be multiplexed with the existing profiles in a single RFchannel through a future extension frame (FEF). The details of each PHYprofile are described below.

1. Base Profile

The base profile represents a main use case for fixed receiving devicesthat are usually connected to a roof-top antenna. The base profile alsoincludes portable devices that could be transported to a place butbelong to a relatively stationary reception category. Use of the baseprofile could be extended to handheld devices or even vehicular by someimproved implementations, but those use cases are not expected for thebase profile receiver operation.

Target SNR range of reception is from approximately 10 to 20 dB, whichincludes the 15 dB SNR reception capability of the existing broadcastsystem (e.g. ATSC A/53). The receiver complexity and power consumptionis not as critical as in the battery-operated handheld devices, whichwill use the handheld profile. Key system parameters for the baseprofile are listed in below table 1.

TABLE 1 LDPC codeword length 16K, 64K bits Constellation size 4~10 bpcu(bits per channel use) Time de-interleaving memory size ≤219 data cellsPilot patterns Pilot pattern for fixed reception FFT size 16K, 32Kpoints

2. Handheld Profile

The handheld profile is designed for use in handheld and vehiculardevices that operate with battery power. The devices can be moving withpedestrian or vehicle speed. The power consumption as well as thereceiver complexity is very important for the implementation of thedevices of the handheld profile. The target SNR range of the handheldprofile is approximately 0 to 10 dB, but can be configured to reachbelow 0 dB when intended for deeper indoor reception.

In addition to low SNR capability, resilience to the Doppler Effectcaused by receiver mobility is the most important performance attributeof the handheld profile. Key system parameters for the handheld profileare listed in the below table 2.

TABLE 2 LDPC codeword length 16K bits Constellation size 2~8 bpcu Timede-interleaving memory size ≤218 data cells Pilot patterns Pilotpatterns for mobile and indoor reception FFT size 8K, 16K points

3. Advanced Profile

The advanced profile provides highest channel capacity at the cost ofmore implementation complexity. This profile requires using MIMOtransmission and reception, and UHDTV service is a target use case forwhich this profile is specifically designed. The increased capacity canalso be used to allow an increased number of services in a givenbandwidth, e.g., multiple SDTV or HDTV services.

The target SNR range of the advanced profile is approximately 20 to 30dB. MIMO transmission may initially use existing elliptically-polarizedtransmission equipment, with extension to full-power cross-polarizedtransmission in the future. Key system parameters for the advancedprofile are listed in below table 3.

TABLE 3 LDPC codeword length 16K, 64K bits Constellation size 8~12 bpcuTime de-interleaving memory size ≤219 data cells Pilot patterns Pilotpattern for fixed reception FFT size 16K, 32K points

In this case, the base profile can be used as a profile for both theterrestrial broadcast service and the mobile broadcast service. That is,the base profile can be used to define a concept of a profile whichincludes the mobile profile. Also, the advanced profile can be dividedadvanced profile for a base profile with MIMO and advanced profile for ahandheld profile with MIMO. Moreover, the three profiles can be changedaccording to intention of the designer.

The following terms and definitions may apply to the present invention.The following terms and definitions can be changed according to design.

auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators

base data pipe: data pipe that carries service signaling data

baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding)

cell: modulation value that is carried by one carrier of the OFDMtransmission

coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data

data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or multiple service(s) orservice component(s).

data pipe unit: a basic unit for allocating data cells to a DP in aframe.

data symbol: OFDM symbol in a frame which is not a preamble symbol (theframe signaling symbol and frame edge symbol is included in the datasymbol)

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID

dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams

emergency alert channel: part of a frame that carries EAS informationdata

frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol

frame repetition unit: a set of frames belonging to same or differentphysical layer profile including a FEF, which is repeated eight times ina super-frame

fast information channel: a logical channel in a frame that carries themapping information between a service and the corresponding base DP

FECBLOCK: set of LDPC-encoded bits of a DP data

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of the elementary period T

frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data

frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern

frame-group: the set of all the frames having the same PHY profile typein a super-frame.

future extension frame: physical layer time slot within the super-framethat could be used for future extension, which starts with a preamble

Futurecast UTB system: proposed physical layer broadcasting system, ofwhich the input is one or more MPEG2-TS or IP or general stream(s) andof which the output is an RF signal

input stream: A stream of data for an ensemble of services delivered tothe end users by the system.

normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol

PHY profile: subset of all configurations that a corresponding receivershould implement

PLS: physical layer signaling data consisting of PLS1 and PLS2

PLS1: a first set of PLS data carried in the FSS symbols having a fixedsize, coding and modulation, which carries basic information about thesystem as well as the parameters needed to decode the PLS2

NOTE: PLS1 data remains constant for the duration of a frame-group.

PLS2: a second set of PLS data transmitted in the FSS symbol, whichcarries more detailed PLS data about the system and the DPs

PLS2 dynamic data: PLS2 data that may dynamically change frame-by-frame

PLS2 static data: PLS2 data that remains static for the duration of aframe-group

preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system

preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located in the beginning of a frame

NOTE: The preamble symbol is mainly used for fast initial band scan todetect the system signal, its timing, frequency offset, and FFT-size.

reserved for future use: not defined by the present document but may bedefined in future

super-frame: set of eight frame repetition units

time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of the timeinterleaver memory

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs

NOTE: The TI group may be mapped directly to one frame or may be mappedto multiple frames. It may contain one or more TI blocks.

Type 1 DP: DP of a frame where all DPs are mapped into the frame in TDMfashion

Type 2 DP: DP of a frame where all DPs are mapped into the frame in FDMfashion

XFECBLOCK: set of Ncells cells carrying all the bits of one LDPCFECBLOCK

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

The apparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can includean input formatting block 1000, a BICM (Bit interleaved coding &modulation) block 1010, a frame building block 1020, an OFDM (OrthogonalFrequency Division Multiplexing) generation block 1030 and a signalinggeneration block 1040. A description will be given of the operation ofeach module of the apparatus for transmitting broadcast signals.

IP stream/packets and MPEG2-TS are the main input formats, other streamtypes are handled as General Streams. In addition to these data inputs,Management Information is input to control the scheduling and allocationof the corresponding bandwidth for each input stream. One or multiple TSstream(s), IP stream(s) and/or General Stream(s) inputs aresimultaneously allowed.

The input formatting block 1000 can demultiplex each input stream intoone or multiple data pipe(s), to each of which an independent coding andmodulation is applied. The data pipe (DP) is the basic unit forrobustness control, thereby affecting quality-of-service (QoS). One ormultiple service(s) or service component(s) can be carried by a singleDP. Details of operations of the input formatting block 1000 will bedescribed later.

The data pipe is a logical channel in the physical layer that carriesservice data or related metadata, which may carry one or multipleservice(s) or service component(s).

Also, the data pipe unit: a basic unit for allocating data cells to a DPin a frame.

In the BICM block 1010, parity data is added for error correction andthe encoded bit streams are mapped to complex-value constellationsymbols. The symbols are interleaved across a specific interleavingdepth that is used for the corresponding DP. For the advanced profile,MIMO encoding is performed in the BICM block 1010 and the additionaldata path is added at the output for MIMO transmission. Details ofoperations of the BICM block 1010 will be described later.

The Frame Building block 1020 can map the data cells of the input DPsinto the OFDM symbols within a frame. After mapping, the frequencyinterleaving is used for frequency-domain diversity, especially tocombat frequency-selective fading channels. Details of operations of theFrame Building block 1020 will be described later.

After inserting a preamble at the beginning of each frame, the OFDMGeneration block 1030 can apply conventional OFDM modulation having acyclic prefix as guard interval. For antenna space diversity, adistributed MISO scheme is applied across the transmitters. In addition,a Peak-to-Average Power Reduction (PAPR) scheme is performed in the timedomain. For flexible network planning, this proposal provides a set ofvarious FFT sizes, guard interval lengths and corresponding pilotpatterns. Details of operations of the OFDM Generation block 1030 willbe described later.

The Signaling Generation block 1040 can create physical layer signalinginformation used for the operation of each functional block. Thissignaling information is also transmitted so that the services ofinterest are properly recovered at the receiver side. Details ofoperations of the Signaling Generation block 1040 will be describedlater.

FIGS. 2, 3 and 4 illustrate the input formatting block 1000 according toembodiments of the present invention. A description will be given ofeach figure.

FIG. 2, including views (a) and (b), illustrates an input formattingblock and a signaling generation block according to one embodiment ofthe present invention.

The input formatting block illustrated in FIG. 2(a) corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

The input to the physical layer may be composed of one or multiple datastreams. Each data stream is carried by one DP. The mode adaptationmodules slice the incoming data stream into data fields of the basebandframe (BBF). The system supports three types of input data streams: aMPEG2-TS stream, an Internet protocol (IP) stream and a Generic stream(GS). The MPEG2-TS stream is characterized by fixed length (188 byte)packets with the first byte being a sync-byte (0×47). The IP stream iscomposed of variable length IP datagram packets, as signaled within IPpacket headers. The system supports both IPv4 and IPv6 for the IPstream. The GS stream may be composed of variable length packets orconstant length packets, signaled within encapsulation packet headers.

FIG. 2(a) shows a mode adaptation block 2000 and a stream adaptationblock 2010 for signal DP, and FIG. 2(b) shows a physical layer signaling(PLS) generation block 2020 and PLS scramblers 2030 for generating andprocessing PLS data. A description will be given of the operation ofeach block.

The input TS, IP and GS streams are split into multiple service orservice component (audio, video, etc.) streams. The mode adaptationblock 2000 is comprised of a CRC Encoder 2002, a BB (baseband) FrameSlicer 2004, and a BB Frame Header Insertion block 2006.

The CRC Encoder 2002 provides three kinds of CRC encoding for errordetection at the user packet (UP) level, i.e., CRC-8, CRC-16, andCRC-32. The computed CRC bytes are appended after the UP. CRC-8 is usedfor TS stream and CRC-32 for IP stream. If the GS stream doesn't providethe CRC encoding, the proposed CRC encoding should be applied.

The BB Frame Slicer 2004 maps the input into an internal logical-bitformat. The first received bit is defined to be the MSB. The BB FrameSlicer 2004 allocates a number of input bits equal to the available datafield capacity. To allocate a number of input bits equal to the BBFpayload, the UP packet stream is sliced to fit the data field of BBF.

The BB Frame Header Insertion block 2006 can insert fixed length BBFheader of 2 bytes is inserted in front of the BB Frame. The BBF headeris composed of STUFFI (1 bit), SYNCD (13 bits), and RFU (2 bits). Inaddition to the fixed 2-Byte BBF header, BBF can have an extension field(1 or 3 bytes) at the end of the 2-byte BBF header.

The stream adaptation 2010 is comprised of a stuffing insertion block2012 and a BB frame scrambler 2014. The stuffing insertion block 2012can insert stuffing field into a payload of a BB frame. If the inputdata to the stream adaptation is sufficient to fill a BB-Frame, STUFFIis set to ‘0’ and the BBF has no stuffing field. Otherwise STUFFI is setto ‘1’ and the stuffing field is inserted immediately after the BBFheader. The stuffing field comprises two bytes of the stuffing fieldheader and a variable size of stuffing data.

The BB frame scrambler 2014 scrambles complete BBF for energy dispersal.The scrambling sequence is synchronous with the BBF. The scramblingsequence is generated by a feed-back shift register.

The signaling generation block illustrated in FIG. 2(b) corresponds toan embodiment of the signaling generation block 1040 described withreference to FIG. 1. The PLS generation block 2020 can generate physicallayer signaling (PLS) data. The PLS provides the receiver with a meansto access physical layer DPs. The PLS data consists of PLS1 data andPLS2 data.

The PLS1 data is a first set of PLS data carried in the FSS symbols inthe frame having a fixed size, coding and modulation, which carriesbasic information about the system as well as the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable the reception anddecoding of the PLS2 data. Also, the PLS1 data remains constant for theduration of a frame-group.

The PLS2 data is a second set of PLS data transmitted in the FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode the desired DP. The PLS2 signaling further consistsof two types of parameters, PLS2 Static data (PLS2-STAT data) and PLS2dynamic data (PLS2-DYN data). The PLS2 Static data is PLS2 data thatremains static for the duration of a frame-group and the PLS2 dynamicdata is PLS2 data that may dynamically change frame-by-frame.

Details of the PLS data will be described later.

The PLS scramblers 2030 can scramble the generated PLS data for energydispersal.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

The input formatting block illustrated in FIG. 3 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

FIG. 3 shows a mode adaptation block of the input formatting block whenthe input signal corresponds to multiple input streams.

The mode adaptation block of the input formatting block for processingthe multiple input streams can independently process the multiple inputstreams.

Referring to FIG. 3, the mode adaptation block for respectivelyprocessing the multiple input streams can include an input streamsplitter 3000, an input stream synchronizer 3010, a compensating delayblock 3020, a null packet deletion block 3030, a head compression block3040, a CRC encoder 3050, a BB frame slicer 3060 and a BB headerinsertion block 3070. Description will be given of each block of themode adaptation block.

Operations of the CRC encoder 3050, BB frame slicer 3060 and BB headerinsertion block 3070 correspond to those of the CRC encoder, BB frameslicer and BB header insertion block described with reference to FIG. 2and thus description thereof is omitted.

The input stream splitter 3000 can split the input TS, IP, GS streamsinto multiple service or service component (audio, video, etc.) streams.

The input stream synchronizer 3010 may be referred as ISSY. The ISSY canprovide suitable means to guarantee Constant Bit Rate (CBR) and constantend-to-end transmission delay for any input data format. The ISSY isalways used for the case of multiple DPs carrying TS, and optionallyused for multiple DPs carrying GS streams.

The compensating delay block 3020 can delay the split TS packet streamfollowing the insertion of ISSY information to allow a TS packetrecombining mechanism without requiring additional memory in thereceiver.

The null packet deletion block 3030, is used only for the TS inputstream case. Some TS input streams or split TS streams may have a largenumber of null-packets present in order to accommodate VBR (variablebit-rate) services in a CBR TS stream. In this case, in order to avoidunnecessary transmission overhead, null-packets can be identified andnot transmitted. In the receiver, removed null-packets can bere-inserted in the exact place where they were originally by referenceto a deleted null-packet (DNP) counter that is inserted in thetransmission, thus guaranteeing constant bit-rate and avoiding the needfor time-stamp (PCR) updating.

The head compression block 3040 can provide packet header compression toincrease transmission efficiency for TS or IP input streams. Because thereceiver can have a priori information on certain parts of the header,this known information can be deleted in the transmitter.

For Transport Stream, the receiver has a-priori information about thesync-byte configuration (0×47) and the packet length (188 Byte). If theinput TS stream carries content that has only one PID, i.e., for onlyone service component (video, audio, etc.) or service sub-component (SVCbase layer, SVC enhancement layer, MVC base view or MVC dependentviews), TS packet header compression can be applied (optionally) to theTransport Stream. IP packet header compression is used optionally if theinput steam is an IP stream. The above-described blocks may be omittedor replaced by blocks having similar or identical functions.

FIG. 4, including views (a) and (b), illustrates a BICM block accordingto an embodiment of the present invention

The BICM block illustrated in FIG. 4 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

As described above, the apparatus for transmitting broadcast signals forfuture broadcast services according to an embodiment of the presentinvention can provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS (quality of service) depends on characteristics of a serviceprovided by the apparatus for transmitting broadcast signals for futurebroadcast services according to an embodiment of the present invention,data corresponding to respective services needs to be processed throughdifferent schemes. Accordingly, the a BICM block according to anembodiment of the present invention can independently process DPs inputthereto by independently applying SISO, MISO and MIMO schemes to thedata pipes respectively corresponding to data paths. Consequently, theapparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can controlQoS for each service or service component transmitted through each DP.

FIG. 4(a) shows the BICM block shared by the base profile and thehandheld profile, and FIG. 4(b) shows the BICM block of the advancedprofile.

The BICM block shared by the base profile and the handheld profile andthe BICM block of the advanced profile can include plural processingblocks for processing each DP.

A description will be given of each processing block of the BICM blockfor the base profile and the handheld profile and the BICM block for theadvanced profile.

A processing block 5000 of the BICM block for the base profile and thehandheld profile can include a Data FEC encoder 5010, a bit interleaver5020, a constellation mapper 5030, an SSD (Signal Space Diversity)encoding block 5040 and a time interleaver 5050.

The Data FEC encoder 5010 can perform the FEC encoding on the input BBFto generate FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The outer coding (BCH) is optional coding method. Detailsof operations of the Data FEC encoder 5010 will be described later.

The bit interleaver 5020 can interleave outputs of the Data FEC encoder5010 to achieve optimized performance with combination of the LDPC codesand modulation scheme while providing an efficiently implementablestructure. Details of operations of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 can modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or cell wordfrom a cell-word demultiplexer 5060-1 in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) to give apower-normalized constellation point, el. This constellation mapping isapplied only for DPs. Observe that QAM-16 and NUQs are square shaped,while NUCs have arbitrary shape. When each constellation is rotated byany multiple of 90 degrees, the rotated constellation exactly overlapswith its original one. This “rotation-sense” symmetric property makesthe capacities and the average powers of the real and imaginarycomponents equal to each other. Both NUQs and NUCs are definedspecifically for each code rate and the particular one used is signaledby the parameter DP MOD filed in PLS2 data.

After the output of the constellation mapper 5030 is processed by theSSD encoding block 5040, the time interleaver 5050 can operate at the DPlevel. The parameters of time interleaving (TI) may be set differentlyfor each DP. Details of operations of the time interleaver 5050 will bedescribed later.

A processing block 5000-1 of the BICM block for the advanced profile caninclude a Data FEC encoder 5010-1, a bit interleaver 5020-1,constellation mappers 5030-1 and time interleavers 5050-1.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 by further including the a cell-word demultiplexer5060-1 and a MIMO encoding block 5070-1.

Also, the operations of the Data FEC encoder 5010-1, bit interleaver5020-1, constellation mappers 5030-1, and time interleavers 5050-1 inthe processing block 5000-1 correspond to those of the Data FEC encoder5010, bit interleaver 5020, constellation mapper 5030, and timeinterleaver 5050 of the processing block 5000 described above, and thusdescription thereof is omitted.

The cell-word demultiplexer 5060-1 is used for the DP of the advancedprofile to divide the single cell-word stream into dual cell-wordstreams for MIMO processing. Details of operations of the cell-worddemultiplexer 5010-1 will be described later.

The MIMO encoding block 5070-1 is used to process the output of thecell-word demultiplexer 5060-1 using a MIMO encoding scheme. The MIMOencoding scheme was optimized for broadcasting signal transmission. TheMIMO technology is a promising way to get a capacity increase but itdepends on channel characteristics. Especially for broadcasting, thestrong LOS component of the channel or a difference in the receivedsignal power between two antennas caused by different signal propagationcharacteristics makes it difficult to get capacity gain from MIMO. Theproposed MIMO encoding scheme overcomes this problem using arotation-based pre-coding and phase randomization of one of the MIMOoutput signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. Two MIMO encodingmodes are defined in this proposal; full-rate spatial multiplexing(FR-SM) and full-rate full-diversity spatial multiplexing (FRFD-SM). TheFR-SM encoding provides capacity increase with relatively smallcomplexity increase at the receiver side while the FRFD-SM encodingprovides capacity increase and additional diversity gain with a greatcomplexity increase at the receiver side. The proposed MIMO encodingscheme has no restriction on the antenna polarity configuration.

MIMO processing is required for the advanced profile frame, which meansall DPs in the advanced profile frame are processed by the MIMO encoder.MIMO processing is applied at DP level. Pairs of the ConstellationMapper outputs NUQ (e1,i and e2,i) are fed to the input of the MIMOEncoder. Paired MIMO Encoder output (g1,i and g2,i) is transmitted bythe same carrier k and OFDM symbol 1 of their respective TX antennas.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 5 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 6 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

FIG. 5 illustrates a BICM block for protection of physical layersignaling (PLS), emergency alert channel (EAC) and fast informationchannel (FIC). EAC is a part of a frame that carries EAS informationdata and FIC is a logical channel in a frame that carries the mappinginformation between a service and the corresponding base DP. Details ofthe EAC and FIC_will be described later.

Referring to FIG. 6, the BICM block for protection of PLS, EAC andFIC_can include a PLS FEC encoder 6000, a bit interleaver 6010 and aconstellation mapper 6020.

Also, the PLS FEC encoder 6000 can include a scrambler 6002, a BCHencoding/zero insertion block 6005, an LDPC encoding block 6006 and anLDPC parity puncturing block. Bit interleaving 6012 and constellationmapping 6022 are then performed. Description will be given of each blockof the BICM block.

The PLS FEC encoder 6000 can encode the scrambled PLS 1/2 data, EAC andFIC_section.

The scrambler can scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block can perform outer encoding on thescrambled PLS 1/2 data using the shortened BCH code for PLS protectionand insert zero bits after the BCH encoding. For PLS1 data only, theoutput bits of the zero insertion may be permutted before LDPC encoding.

The LDPC encoding block can encode the output of the BCH encoding/zeroinsertion block using LDPC code. To generate a complete coded block,Cldpc, parity bits, Pldpc are encoded systematically from eachzero-inserted PLS information block, Ildpc and appended after it.C _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ , i ₁ , . . . , i _(K) _(ldpc) ⁻¹ ,p ₀ , p ₁ , . . . , p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 1]

The LDPC code parameters for PLS1 and PLS2 are as following table 4.

TABLE 4 Signaling Nbch_ Kldpc Nldpc code Type Ksig Kbch parity (=Nbch)Nldpc parity rate Qldpc PLS1  342 1020 60 1080 4320 3240 1/4 36 PLS2<1021 >1020 2100 2160 7200 5040 3/10 56

The LDPC parity puncturing block can perform puncturing on the PLS1 dataand PLS 2 data

When shortening is applied to the PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. Also, for the PLS2 dataprotection, the LDPC parity bits of PLS2 are punctured after LDPCencoding. These punctured bits are not transmitted.

The bit interleaver 6010 can interleave the each shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 can map the bit interleaved PLS1 data andPLS2 data onto constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 6 illustrates a frame building block according to one embodiment ofthe present invention.

The frame building block illustrated in FIG. 6 corresponds to anembodiment of the frame building block 1020 described with reference toFIG. 1.

Referring to FIG. 6, the frame building block can include a delaycompensation block 7000, a cell mapper 7010 and a frequency interleaver7020. Description will be given of each block of the frame buildingblock.

The delay compensation block 7000 can adjust the timing between the datapipes and the corresponding PLS data to ensure that they are co-timed atthe transmitter end. The PLS data is delayed by the same amount as datapipes are by addressing the delays of data pipes caused by the InputFormatting block and BICM block. The delay of the BICM block is mainlydue to the time interleaver 5050. In-band signaling data carriesinformation of the next TI group so that they are carried one frameahead of the DPs to be signaled. The Delay Compensating block delaysin-band signaling data accordingly.

The cell mapper 7010 includes an assembly of PLS cells 7002, an assemblyof EAS cells 7004, an assembly of FIC cells 7006, an assembly of Base DPcells 7008, and an assembly of Normal DP cells 7012, and thus can mapPLS, EAC, FIC, DPs, auxiliary streams and dummy cells into the activecarriers of the OFDM symbols in the frame. The basic function of thecell mapper 7010 is to map data cells produced by the TIs for each ofthe DPs, PLS cells, and EAC/FIC cells, if any, into arrays of activeOFDM cells corresponding to each of the OFDM symbols within a frame.Service signaling data (such as PSI (program specific information)/SI)can be separately gathered and sent by a data pipe. The cell mapper 7010operates according to the dynamic information produced by the schedulerand the configuration of the frame structure. Details of the frame willbe described later.

The frequency interleaver 7020 can randomly interleave data cellsreceived from the cell mapper 7010 to provide frequency diversity. Also,the frequency interleaver 7020 can operate on very OFDM symbol paircomprised of two sequential OFDM symbols using a differentinterleaving-seed order to get maximum interleaving gain in a singleframe.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 7 illustrates an OFDM generation block according to an embodimentof the present invention.

The OFDM generation block illustrated in FIG. 7 corresponds to anembodiment of the OFDM generation block 1030 described with reference toFIG. 1.

The OFDM generation block modulates the OFDM carriers by the cellsproduced by the Frame Building block, inserts the pilots, and producesthe time domain signal for transmission. Also, this block subsequentlyinserts guard intervals, and applies PAPR (Peak-to-Average Power Radio)reduction processing to produce the final RF signal.

Referring to FIG. 7, the OFDM generation block can include a pilot andreserved tone insertion block 8000, a 2D-eSFN encoding block 8010, anIFFT (Inverse Fast Fourier Transform) block 8020, a PAPR reduction block8030, a guard interval insertion block 8040, a preamble insertion block8050, other system insertion block 8060 and a DAC block 8070.

The other system insertion block 8060 can multiplex signals of aplurality of broadcast transmission/reception systems in the time domainsuch that data of two or more different broadcast transmission/receptionsystems providing broadcast services can be simultaneously transmittedin the same RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

FIG. 8 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention cancorrespond to the apparatus for transmitting broadcast signals forfuture broadcast services, described with reference to FIG. 1.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention can includea synchronization & demodulation module 9000, a frame parsing module9010, a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the apparatus for receiving broadcast signals.

The synchronization & demodulation module 9000 can receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the apparatus for receivingbroadcast signals and carry out demodulation corresponding to a reverseprocedure of the procedure performed by the apparatus for transmittingbroadcast signals.

The frame parsing module 9010 can parse input signal frames and extractdata through which a service selected by a user is transmitted. If theapparatus for transmitting broadcast signals performs interleaving, theframe parsing module 9010 can carry out deinterleaving corresponding toa reverse procedure of interleaving. In this case, the positions of asignal and data that need to be extracted can be obtained by decodingdata output from the signaling decoding module 9040 to restorescheduling information generated by the apparatus for transmittingbroadcast signals.

The demapping & decoding module 9020 can convert the input signals intobit domain data and then deinterleave the same as necessary. Thedemapping & decoding module 9020 can perform demapping for mappingapplied for transmission efficiency and correct an error generated on atransmission channel through decoding. In this case, the demapping &decoding module 9020 can obtain transmission parameters necessary fordemapping and decoding by decoding the data output from the signalingdecoding module 9040.

The output processor 9030 can perform reverse procedures of variouscompression/signal processing procedures which are applied by theapparatus for transmitting broadcast signals to improve transmissionefficiency. In this case, the output processor 9030 can acquirenecessary control information from data output from the signalingdecoding module 9040. The output of the output processor 8300corresponds to a signal input to the apparatus for transmittingbroadcast signals and may be MPEG-TSs, IP streams (v4 or v6) and genericstreams.

The signaling decoding module 9040 can obtain PLS information from thesignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, demapping & decodingmodule 9020 and output processor 9030 can execute functions thereofusing the data output from the signaling decoding module 9040.

FIG. 9 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 9 shows an example configuration of the frame types and FRUs in asuper-frame. (a) shows a super frame according to an embodiment of thepresent invention, (b) shows FRU (Frame Repetition Unit) according to anembodiment of the present invention, (c) shows frames of variable PHYprofiles in the FRU and (d) shows a structure of a frame.

A super-frame may be composed of eight FRUs. The FRU is a basicmultiplexing unit for TDM of the frames, and is repeated eight times ina super-frame.

Each frame in the FRU belongs to one of the PHY profiles, (base,handheld, advanced) or FEF. The maximum allowed number of the frames inthe FRU is four and a given PHY profile can appear any number of timesfrom zero times to four times in the FRU (e.g., base, base, handheld,advanced). PHY profile definitions can be extended using reserved valuesof the PHY PROFILE in the preamble, if required.

The FEF part is inserted at the end of the FRU, if included. When theFEF is included in the FRU, the minimum number of FEFs is 8 in asuper-frame. It is not recommended that FEF parts be adjacent to eachother.

One frame is further divided into a number of OFDM symbols and apreamble. As shown in (d), the frame comprises a preamble, one or moreframe signaling symbols (FSS), normal data symbols and a frame edgesymbol (FES).

The preamble is a special symbol that enables fast Futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of the signal. The detaileddescription of the preamble will be will be described later.

The main purpose of the FSS(s) is to carry the PLS data. For fastsynchronization and channel estimation, and hence fast decoding of PLSdata, the FSS has more dense pilot pattern than the normal data symbol.The FES has exactly the same pilots as the FSS, which enablesfrequency-only interpolation within the FES and temporal interpolation,without extrapolation, for symbols immediately preceding the FES.

FIG. 10 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 10 illustrates the signaling hierarchy structure, which is splitinto three main parts: the preamble signaling data 11000, the PLS1 data11010 and the PLS2 data 11020. The purpose of the preamble, which iscarried by the preamble symbol in every frame, is to indicate thetransmission type and basic transmission parameters of that frame. ThePLS1 enables the receiver to access and decode the PLS2 data, whichcontains the parameters to access the DP of interest. The PLS2 iscarried in every frame and split into two main parts: PLS2-STAT data andPLS2-DYN data. The static and dynamic portion of PLS2 data is followedby padding, if necessary.

FIG. 11 illustrates preamble signaling data according to an embodimentof the present invention.

Preamble signaling data carries 21 bits of information that are neededto enable the receiver to access PLS data and trace DPs within the framestructure. Details of the preamble signaling data are as follows:

PHY_PROFILE: This 3-bit field indicates the PHY profile type of thecurrent frame. The mapping of different PHY profile types is given inbelow table 5.

TABLE 5 Value PHY profile 000 Base profile 001 Handheld profile 010Advanced profiled 011~110 Reserved 111 FEF

FFT_SIZE: This 2 bit field indicates the FFT size of the current framewithin a frame-group, as described in below table 6.

TABLE 6 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3 bit field indicates the guard interval fractionvalue in the current super-frame, as described in below table 7.

TABLE 7 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80101  1/160 110~111 Reserved

EAC_FLAG: This 1 bit field indicates whether the EAC is provided in thecurrent frame. If this field is set to ‘1’, emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, EAS isnot carried in the current frame. This field can be switched dynamicallywithin a super-frame.

PILOT_MODE: This 1-bit field indicates whether the pilot mode is mobilemode or fixed mode for the current frame in the current frame-group. Ifthis field is set to ‘0’, mobile pilot mode is used. If the field is setto ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used forthe current frame in the current frame-group. If this field is set tovalue ‘1’, tone reservation is used for PAPR reduction. If this field isset to ‘0’, PAPR reduction is not used.

FRU_CONFIGURE: This 3-bit field indicates the PHY profile typeconfigurations of the frame repetition units (FRU) that are present inthe current super-frame. All profile types conveyed in the currentsuper-frame are identified in this field in all preambles in the currentsuper-frame. The 3-bit field has a different definition for eachprofile, as show in below table 8.

TABLE 8 Current Current Current PHY_PROFILE = PHY_PROFILE = CurrentPHY_PROFILE = ‘001’ ‘010’ PHY_PROFILE = ‘000’(base) (handheld)(advanced) ‘111’ (FEF) FRU_CONFIGURE = Only base Only handheld Onlyadvanced Only FEF 000 profile present profile present profile presentpresent FRU_CONFIGURE = Handheld Base profile Base profile Base profile1XX profile present present present present FRU_CONFIGURE = AdvancedAdvanced Handheld Handheld X1X profile profile profile profile presentpresent present present FRU_CONFIGURE = FEF FEF FEF Advanced XX1 presentpresent present profile present

RESERVED: This 7-bit field is reserved for future use.

FIG. 12 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable the reception and decoding of the PLS2. As abovementioned, the PLS1 data remain unchanged for the entire duration of oneframe-group. The detailed definition of the signaling fields of the PLS1data are as follows:

PREAMBLE_DATA: This 20-bit field is a copy of the preamble signalingdata excluding the EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates the format of the payload datacarried in the frame-group. PAYLOAD_TYPE is signaled as shown in table9.

TABLE 9 value Payload type 1XX TS stream is transmitted X1X IP stream istransmitted XX1 GS stream is transmitted

NUM_FSS: This 2-bit field indicates the number of FSS symbols in thecurrent frame.

SYSTEM_VERSION: This 8-bit field indicates the version of thetransmitted signal format. The SYSTEM_VERSION is divided into two 4-bitfields, which are a major version and a minor version.

Major version: The MSB four bits of SYSTEM_VERSION field indicate majorversion information. A change in the major version field indicates anon-backward-compatible change. The default value is ‘0000’. For theversion described in this standard, the value is set to ‘0000’.

Minor version: The LSB four bits of SYSTEM_VERSION field indicate minorversion information. A change in the minor version field isbackward-compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may consist of oneor more frequencies, depending on the number of frequencies used perFuturecast UTB system. If the value of the CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies the currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the Futurecast UTBsystem within the ATSC network. The Futurecast UTB system is theterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The Futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same FuturecastUTB system may carry different input streams and use different RFfrequencies in different geographical areas, allowing local serviceinsertion. The frame structure and scheduling is controlled in one placeand is identical for all transmissions within a Futurecast UTB system.One or more Futurecast UTB systems may have the same SYSTEM_ID meaningthat they all have the same physical layer structure and configuration.

The following loop consists of FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate the FRUconfiguration and the length of each frame type. The loop size is fixedso that four PHY profiles (including a FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, the unused fields are filled withzeros.

FRU_PHY_PROFILE: This 3-bit field indicates the PHY profile type of the(i+1)th (i is the loop index) frame of the associated FRU. This fielduses the same signaling format as shown in the table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates the length of the (i+1)thframe of the associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, the exact value of the frame duration can be obtained.

FRU_GI_FRACTION: This 3-bit field indicates the guard interval fractionvalue of the (i+1)th frame of the associated FRU. FRU_GI_FRACTION issignaled according to the table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates the FEC type used by the PLS2protection. The FEC type is signaled according to table 10. The detailsof the LDPC codes will be described later.

TABLE 10 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01~11Reserved

PLS2_MOD: This 3-bit field indicates the modulation type used by thePLS2. The modulation type is signaled according to table 11.

TABLE 11 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100~111Reserved

PLS2_SIZE CELL: This 15-bit field indicates Ctotal_partial_block, thesize (specified as the number of QAM cells) of the collection of fullcoded blocks for PLS2 that is carried in the current frame-group. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates the size, in bits, ofthe PLS2-STAT for the current frame-group. This value is constant duringthe entire duration of the current frame-group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of thePLS2-DYN for the current frame-group. This value is constant during theentire duration of the current frame-group.

PLS2_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetitionmode is used in the current frame-group. When this field is set to value‘1’, the PLS2 repetition mode is activated. When this field is set tovalue ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates Ctotal_partial_block,the size (specified as the number of QAM cells) of the collection ofpartial coded blocks for PLS2 carried in every frame of the currentframe-group, when PLS2 repetition is used. If repetition is not used,the value of this field is equal to 0. This value is constant during theentire duration of the current frame-group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates the FEC type used forPLS2 that is carried in every frame of the next frame-group. The FECtype is signaled according to the table 10.

PLS2_NEXT_MOD: This 3-bit field indicates the modulation type used forPLS2 that is carried in every frame of the next frame-group. Themodulation type is signaled according to the table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in the next frame-group. When this field is setto value ‘1’, the PLS2 repetition mode is activated. When this field isset to value ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates Ctotal_full_block,The size (specified as the number of QAM cells) of the collection offull coded blocks for PLS2 that is carried in every frame of the nextframe-group, when PLS2 repetition is used. If repetition is not used inthe next frame-group, the value of this field is equal to 0. This valueis constant during the entire duration of the current frame-group.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-STAT for the next frame-group. This value is constantin the current frame-group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for the next frame-group. This value is constantin the current frame-group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in the current frame-group. This value is constantduring the entire duration of the current frame-group. The below table12 gives the values of this field. When this field is set to ‘00’,additional parity is not used for the PLS2 in the current frame-group.

TABLE 12 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10~11Reserved

PLS2_AP SIZE_CELL: This 15-bit field indicates the size (specified asthe number of QAM cells) of the additional parity bits of the PLS2. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of next frame-group. Thisvalue is constant during the entire duration of the current frame-group.The table 12 defines the values of this field

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates the size (specifiedas the number of QAM cells) of the additional parity bits of the PLS2 inevery frame of the next frame-group. This value is constant during theentire duration of the current frame-group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS1 signaling.

FIG. 13 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 13 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT dataare the same within a frame-group, while the PLS2-DYN data provideinformation that is specific for the current frame.

The details of fields of the PLS2-STAT data are as follows:

FIC_FLAG: This 1-bit field indicates whether the FIC is used in thecurrent frame-group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofthe current frame-group.

AUX_FLAG: This 1-bit field indicates whether the auxiliary stream(s) isused in the current frame-group. If this field is set to ‘1’, theauxiliary stream is provided in the current frame. If this field set to‘0’, the auxiliary stream is not carried in the current frame. Thisvalue is constant during the entire duration of current frame-group.

NUM_DP: This 6-bit field indicates the number of DPs carried within thecurrent frame. The value of this field ranges from 1 to 64, and thenumber of DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates the type of the DP. This is signaledaccording to the below table 13.

TABLE 13 Value DP Type 000 DP Type 1 001 DP Type 2 010~111 reserved

DP_GROUP_ID: This 8-bit field identifies the DP group with which thecurrent DP is associated. This can be used by a receiver to access theDPs of the service components associated with a particular service,which will have the same DP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates the DP carrying service signalingdata (such as PSI/SI) used in the Management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with the service data or a dedicated DP carrying only the servicesignaling data

DP_FEC_TYPE: This 2-bit field indicates the FEC type used by theassociated DP. The FEC type is signaled according to the below table 14.

TABLE 14 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10~11 Reserved

DP_COD: This 4-bit field indicates the code rate used by the associatedDP. The code rate is signaled according to the below table 15.

TABLE 15 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 01009/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001~1111 Reserved

DP_MOD: This 4-bit field indicates the modulation used by the associatedDP. The modulation is signaled according to the below table 16.

TABLE 16 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-10241001~1111 reserved

DP_SSD_FLAG: This 1-bit field indicates whether the SSD mode is used inthe associated DP. If this field is set to value ‘1’, SSD is used. Ifthis field is set to value ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to the associated DP. The type of MIMO encoding process issignaled according to the table 17.

TABLE 17 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010~111 reserved

DP_TI_TYPE: This 1-bit field indicates the type of time-interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI-blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI-block.

DP_TI_LENGTH: The use of this 2-bit field (the allowed values are only1, 2, 4, 8) is determined by the values set within the DP_TI_TYPE fieldas follows:

If the DP_TI_TYPE is set to the value ‘1’, this field indicates PI, thenumber of the frames to which each TI group is mapped, and there is oneTI-block per TI group (NTI=1). The allowed PI values with 2-bit fieldare defined in the below table 18.

If the DP_TI_TYPE is set to the value ‘0’, this field indicates thenumber of TI-blocks NTI per TI group, and there is one TI group perframe (PI=1). The allowed PI values with 2-bit field are defined in thebelow table 18.

TABLE 18 2-bit field PI NTI 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates the frame interval (HUMP)within the frame-group for the associated DP and the allowed values are1, 2, 4, 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’, or ‘11’,respectively). For DPs that do not appear every frame of theframe-group, the value of this field is equal to the interval betweensuccessive frames. For example, if a DP appears on the frames 1, 5, 9,13, etc., this field is set to ‘4’. For DPs that appear in every frame,this field is set to ‘1’.

DP_TI_BYPASS: This 1-bit field determines the availability of timeinterleaver 5050. If time interleaving is not used for a DP, it is setto ‘1’. Whereas if time interleaving is used it is set to ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates the index of the firstframe of the super-frame in which the current DP occurs. The value ofDP_FIRST_FRAME_IDX ranges from 0 to 31

DP_NUM_BLOCK_MAX: This 10-bit field indicates the maximum value ofDP_NUM_BLOCKS for this DP. The value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates the type of the payload datacarried by the given DP. DP_PAYLOAD_TYPE is signaled according to thebelow table 19.

TABLE 19 Value Payload Type 00 TS. 01 IP 10 GS 11 reserved

DP_INBAND MODE: This 2-bit field indicates whether the current DPcarries in-band signaling information. The in-band signaling type issignaled according to the below table 20.

TABLE 20 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried only 10 INBAND-ISSY is carried only 11 INBAND-PLSand INBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates the protocol type of thepayload carried by the given DP. It is signaled according to the belowtable 21 when input payload types are selected.

TABLE 21 If If If DP_PAYLOAD_TYPE DP_PAYLOAD_TYPE DP_PAYLOAD_TYPE ValueIs TS Is IP Is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6 Reserved 10Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inthe Input Formatting block. The CRC mode is signaled according to thebelow table 22.

TABLE 22 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates the null-packet deletion mode usedby the associated DP when DP_PAYLOAD_TYPE is set to TS (00′). DNP_MODEis signaled according to the below table 23. If DP_PAYLOAD_TYPE is notTS (00′), DNP_MODE is set to the value ‘00’.

TABLE 23 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 reserved

ISSY_MODE: This 2-bit field indicates the ISSY mode used by theassociated DP when DP_PAYLOAD_TYPE is set to TS (00′). The ISSY_MODE issignaled according to the below table 24 If DP_PAYLOAD_TYPE is not TS(00′), ISSY_MODE is set to the value ‘00’.

TABLE 24 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 reserved

HC_MODE_TS: This 2-bit field indicates the TS header compression modeused by the associated DP when DP_PAYLOAD_TYPE is set to TS (00′). TheHC_MODE_TS is signaled according to the below table 25.

TABLE 25 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

TABLE 26 Value Header compression mode 00 No compression 01 HC_MODE_IP 110~11 reserved

PID : This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (00′) and HC MODE TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if FIC_FLAG is equal to ‘1’:

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if AUX_FLAG is equal to ‘1’:

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary streams are used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicatingthe type of the current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 14 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 14 illustrates PLS2-DYN data of the PLS2 data. The values of thePLS2-DYN data may change during the duration of one frame-group, whilethe size of fields remains constant.

The details of fields of the PLS2-DYN data are as follows:

FRAME_INDEX: This 5-bit field indicates the frame index of the currentframe within the super-frame. The index of the first frame of thesuper-frame is set to ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration will change. The nextsuper-frame with changes in the configuration is indicated by the valuesignaled within this field. If this field is set to the value ‘0000’, itmeans that no scheduled change is foreseen: e.g., value ‘1’ indicatesthat there is a change in the next super-frame.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration (i.e., the contents of theFIC) will change. The next super-frame with changes in the configurationis indicated by the value signaled within this field. If this field isset to the value ‘0000’, it means that no scheduled change is foreseen:e.g. value ‘0001’ indicates that there is a change in the nextsuper-frame.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in the loop over NUM_DP, which describe theparameters associated with the DP carried in the current frame.

DP_ID: This 6-bit field indicates uniquely the DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates the start position ofthe first of the DPs using the DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the below table 27.

TABLE 27 DP START field size PHY profile 64K 16K Base 13 bit 15 bitHandheld — 13 bit Advanced 13 bit 15 bit

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks inthe current TI group for the current DP. The value of DP_NUM_BLOCKranges from 0 to 1023

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate the FIC_parameters associated with theEAC.

EAC FLAG: This 1-bit field indicates the existence of the EAC in thecurrent frame. This bit is the same value as the EAC_FLAG in thepreamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates the version numberof a wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated for EAC_LENGTH_BYTE field. If the EAC_FLAG field is equal to‘0’, the following 12 bits are allocated for EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates the length, in byte, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of the frames beforethe frame where the EAC arrives.

The following field appears only if the AUX_FLAG field is equal to ‘1’:

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. The meaning of this field depends on thevalue of AUX_STREAM_TYPE in the configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 15 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped into the active carriers of the OFDM symbols in theframe. The PLS1 and PLS2 are first mapped into one or more FSS(s). Afterthat, EAC cells, if any, are mapped immediately following the PLS field,followed next by FIC cells, if any. The DPs are mapped next after thePLS or EAC, FIC, if any. Type 1 DPs follows first, and Type 2 DPs next.The details of a type of the DP will be described later. In some case,DPs may carry some special data for EAS or service signaling data. Theauxiliary stream or streams, if any, follow the DPs, which in turn arefollowed by dummy cells. Mapping them all together in the abovementioned order, i.e. PLS, EAC, FIC, DPs, auxiliary streams and dummydata cells exactly fill the cell capacity in the frame.

FIG. 16 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to the active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) NFSS is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) has higher density ofpilots allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the NFSS FSS(s) in a top-downmanner as shown in an example in FIG. 16. The PLS1 cells are mappedfirst from the first cell of the first FSS in an increasing order of thecell index. The PLS2 cells follow immediately after the last cell of thePLS1 and mapping continues downward until the last cell index of thefirst FSS. If the total number of required PLS cells exceeds the numberof active carriers of one FSS, mapping proceeds to the next FSS andcontinues in exactly the same manner as the first FSS.

After PLS mapping is completed, DPs are carried next. If EAC, FIC orboth are present in the current frame, they are placed between PLS and“normal” DPs.

FIG. 17 illustrates EAC mapping according to an embodiment of thepresent invention.

EAC is a dedicated channel for carrying EAS messages and links to theDPs for EAS. EAS support is provided but EAC itself may or may not bepresent in every frame. EAC, if any, is mapped immediately after thePLS2 cells. EAC is not preceded by any of the FIC, DPs, auxiliarystreams or dummy cells other than the PLS cells. The procedure ofmapping the EAC cells is exactly the same as that of the PLS.

The EAC cells are mapped from the next cell of the PLS2 in increasingorder of the cell index as shown in the example in FIG. 17. Depending onthe EAS message size, EAC cells may occupy a few symbols, as shown inFIG. 17.

EAC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required EAC cells exceeds the number of remainingactive carriers of the last FSS mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol, which has more activecarriers than a FSS.

After EAC mapping is completed, the FIC is carried next, if any exists.If FIC is not transmitted (as signaled in the PLS2 field), DPs followimmediately after the last cell of the EAC.

FIG. 18 illustrates FIC mapping according to an embodiment of thepresent invention.

(a) shows an example mapping of FIC cell without EAC and (b) shows anexample mapping of FIC cell with EAC.

FIC is a dedicated channel for carrying cross-layer information toenable fast service acquisition and channel scanning. This informationprimarily includes channel binding information between DPs and theservices of each broadcaster. For fast scan, a receiver can decode FICand obtain information such as broadcaster ID, number of services, andBASE_DP_ID. For fast service acquisition, in addition to FIC, base DPcan be decoded using BASE_DP_ID. Other than the content it carries, abase DP is encoded and mapped to a frame in exactly the same way as anormal DP. Therefore, no additional description is required for a baseDP. The FIC data is generated and consumed in the Management Layer. Thecontent of FIC data is as described in the Management Layerspecification.

The FIC data is optional and the use of FIC is signaled by the FIC_FLAGparameter in the static part of the PLS2. If FIC is used, FIC_FLAG isset to ‘1’ and the signaling field for FIC is defined in the static partof PLS2. Signaled in this field are FIC_VERSION, and FIC_LENGTH_BYTE.FIC_uses the same modulation, coding and time interleaving parameters asPLS2. FIC_shares the same signaling parameters such as PLS2 MOD and PLS2FEC. FIC data, if any, is mapped immediately after PLS2 or EAC if any.FIC is not preceded by any normal DPs, auxiliary streams or dummy cells.The method of mapping FIC cells is exactly the same as that of EAC whichis again the same as PLS.

Without EAC after PLS, FIC cells are mapped from the next cell of thePLS2 in an increasing order of the cell index as shown in an example in(a). Depending on the FIC data size, FIC cells may be mapped over a fewsymbols, as shown in (b).

FIC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required FIC cells exceeds the number of remainingactive carriers of the last FSS, mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol which has more activecarriers than a FSS.

If EAS messages are transmitted in the current frame, EAC precedes FIC,and FIC cells are mapped from the next cell of the EAC in an increasingorder of the cell index as shown in (b).

After FIC mapping is completed, one or more DPs are mapped, followed byauxiliary streams, if any, and dummy cells.

FIG. 19 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 19 illustrates an FEC structure according to an embodiment of thepresent invention before bit interleaving. As above mentioned, Data FECencoder may perform the FEC encoding on the input BBF to generateFECBLOCK procedure using outer coding (BCH), and inner coding (LDPC).The illustrated FEC structure corresponds to the FECBLOCK. Also, theFECBLOCK and the FEC structure have same value corresponding to a lengthof LDPC codeword.

The BCH encoding is applied to each BBF (Kbch bits), and then LDPCencoding is applied to BCH-encoded BBF (Kldpc bits=Nbch bits) asillustrated in FIG. 22.

The value of Nldpc is either 64800 bits (long FECBLOCK) or 16200 bits(short FECBLOCK).

The below table 28 and table 29 show FEC encoding parameters for a longFECBLOCK and a short FECBLOCK, respectively.

TABLE 28 BCH error LDPC correction Nbch- Rate Nldpc Kldpc Kbchcapability Kbch 5/15 64800 21600 21408 12 192 6/15 25920 25728 7/1530240 30048 8/15 34560 34368 9/15 38880 38688 10/15  43200 43008 11/15 47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 29 BCH error LDPC correction Nbch- Rate Nldpc Kldpc Kbchcapability Kbch 5/15 16200 5400 5232 12 168 6/15 6480 6312 7/15 75607392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15  11880 1171212/15  12960 12792 13/15  14040 13872

The details of operations of the BCH encoding and LDPC encoding are asfollows:

A 12-error correcting BCH code is used for outer encoding of the BBF.The BCH generator polynomial for short FECBLOCK and long FECBLOCK areobtained by multiplying together all polynomials.

LDPC code is used to encode the output of the outer BCH encoding. Togenerate a completed Bldpc (FECBLOCK), Pldpc (parity bits) is encodedsystematically from each Ildpc (BCH-encoded BBF), and appended to Ildpc.The completed Bldpc (FECBLOCK) is expressed by the following equation.B _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ , i ₁ , . . . , i _(K) _(ldpc) ⁻¹ ,p ₀ , p ₁ , . . . , p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 2]

The parameters for long FECBLOCK and short FECBLOCK are given in theabove table 28 and 29, respectively.

The detailed procedure to calculate Nldpc−Kldpc parity bits for longFECBLOCK, is as follows:

1) Initialize the parity bits,p ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹=0  [Equation 3]

2) Accumulate the first information bit-i0, at parity bit addressesspecified in the first row of an addresses of parity check matrix. Thedetails of addresses of parity check matrix will be described later. Forexample, for rate 13/15:

$\begin{matrix}{{p_{983} = {p_{983} \oplus i_{0}}}{p_{2815} = {p_{2815} \oplus i_{0}}}{p_{4837} = {p_{4837} \oplus i_{0}}}{p_{4989} = {p_{4989} \oplus i_{0}}}{p_{6138} = {p_{6138} \oplus i_{0}}}{p_{6458} = {p_{6458} \oplus i_{0}}}{p_{6921} = {p_{6921} \oplus i_{0}}}{p_{6974} = {p_{6974} \oplus i_{0}}}{p_{7572} = {p_{7572} \oplus i_{0}}}{p_{8260} = {p_{8260} \oplus i_{0}}}{p_{8496} = {p_{8496} \oplus i_{0}}}} & \left\lbrack {{Equation}\mspace{14mu} 4} \right\rbrack\end{matrix}$

3) For the next 359 information bits, is, s=1, 2, . . . , 359 accumulateis at parity bit addresses using following equation.{x+(s mod 360)×

_(ldpc)}mod(N _(ldpc) −K _(ldpc))  [Equation 5]

where x denotes the address of the parity bit accumulator correspondingto the first bit i0, and Qldpc is a code rate dependent constantspecified in the addresses of parity check matrix. Continuing with theexample, Qldpc=24 for rate 13/15, so for information bit i1, thefollowing operations are performed:

$\begin{matrix}{{p_{1007} = {p_{1007} \oplus i_{1}}}{p_{2839} = {p_{2839} \oplus i_{1}}}{p_{4861} = {p_{4861} \oplus i_{1}}}{p_{5013} = {p_{5013} \oplus i_{1}}}{p_{6162} = {p_{6162} \oplus i_{1}}}{p_{6482} = {p_{6482} \oplus i_{1}}}{p_{6945} = {p_{6945} \oplus i_{1}}}{p_{6998} = {p_{6998} \oplus i_{1}}}{p_{7596} = {p_{7596} \oplus i_{1}}}{p_{8284} = {p_{8284} \oplus i_{1}}}{p_{8520} = {p_{8520} \oplus i_{1}}}} & \left\lbrack {{Equation}\mspace{14mu} 6} \right\rbrack\end{matrix}$

4) For the 361st information bit i360, the addresses of the parity bitaccumulators are given in the second row of the addresses of paritycheck matrix. In a similar manner the addresses of the parity bitaccumulators for the following 359 information bits is, s=361, 362, . .. , 719 are obtained using the equation 6, where x denotes the addressof the parity bit accumulator corresponding to the information bit i360,i.e., the entries in the second row of the addresses of parity checkmatrix.

5) In a similar manner, for every group of 360 new information bits, anew row from addresses of parity check matrixes used to find theaddresses of the parity bit accumulators.

After all of the information bits are exhausted, the final parity bitsare obtained as follows:

6) Sequentially perform the following operations starting with i=1p _(i) =p _(i) ⊕p _(i-1) , i=1,2, . . . , N _(ldpc) −K_(ldpc)−1  [Equation 7]

where final content of pi, i=0,1, . . . Nldpc−Kldpc−1 is equal to theparity bit pi.

TABLE 30 Code Rate Qldpc 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for a short FECBLOCK is in accordance withthe LDPC encoding procedure for the long FECBLOCK, except replacing thetable 30 with table 31, and replacing the addresses of parity checkmatrix for the long FECBLOCK with the addresses of parity check matrixfor the short FECBLOCK.

TABLE 31 Code Rate Qldpc 5/15 30 6/15 27 7/15 24 8/15 21 9/15 18 10/15 15 11/15  12 12/15  9 13/15  6

FIG. 20 illustrates a time interleaving according to an embodiment ofthe present invention.

(a) to (c) show examples of TI mode.

The time interleaver operates at the DP level. The parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI:

DP_TI_TYPE (allowed values: 0 or 1): Represents the TI mode; ‘0’indicates the mode with multiple TI blocks (more than one TI block) perTI group. In this case, one TI group is directly mapped to one frame (nointer-frame interleaving). ‘1’ indicates the mode with only one TI blockper TI group. In this case, the TI block may be spread over more thanone frame (inter-frame interleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks NTI per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames PI spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): Represents the maximumnumber of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, 8): Represents the number ofthe frames IJUMP between two successive frames carrying the same DP of agiven PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. It is set to ‘0’ if timeinterleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the Delay Compensation block for the dynamic configuration informationfrom the scheduler will still be required. In each DP, the XFECBLOCKsreceived from the SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and willcontain a dynamically variable number of XFECBLOCKs. The number ofXFECBLOCKs in the TI group of index n is denoted by NxBLOCK_Group(n) andis signaled as DP_NUM_BLOCK in the PLS2-DYN data. Note thatNxBLOCK_Group(n) may vary from the minimum value of 0 to the maximumvalue NxBLOCK_Group_MAX (corresponding to DP_NUM_BLOCK_MAX) of which thelargest value is 1023.

Each TI group is either mapped directly onto one frame or spread over PIframes. Each TI group is also divided into more than one TI blocks(NTI),where each TI block corresponds to one usage of time interleaver memory.The TI blocks within the TI group may contain slightly different numbersof XFECBLOCKs. If the TI group is divided into multiple TI blocks, it isdirectly mapped to only one frame. There are three options for timeinterleaving (except the extra option of skipping the time interleaving)as shown in the below table 32.

TABLE 32 Modes Descriptions Option-1 Each TI group contains one TI blockand is mapped directly to one frame as shown in (a). This option issignaled in the PLS2- STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH =‘1’(NTI = 1). Option-2 Each TI group contains one TI block and is mappedto more than one frame. (b) shows an example, where one TI group ismapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (PI = 2) andDP_FRAME_INTERVAL (IJUMP = 2). This provides greater time diversity forlow data-rate services. This option is signaled in the PLS2-STAT byDP_TI_TYPE = ‘1’. Option-3 Each TI group is divided into multiple TIblocks and is mapped directly to one frame as shown in (c). Each TIblock may use full TI memory, so as to provide the maximum bit-rate fora DP. This option is signaled in the PLS2-STAT signaling by DP_TI_TYPE =‘0’ and DP_TI_LENGTH = NTI, while PI = 1.

Typically, the time interleaver will also act as a buffer for DP dataprior to the process of frame building. This is achieved by means of twomemory banks for each DP. The first TI-block is written to the firstbank. The second TI-block is written to the second bank while the firstbank is being read from and so on.

The TI is a twisted row-column block interleaver. For the sth TI blockof the nth TI group, the number of rows N_(r) of a TI memory is equal tothe number of cells N_(cells) i.e., N_(r)=N_(cells) while the number ofcolumns N_(r) is equal to the number N_(xBLOCK_TI)(n, s)

FIG. 21 illustrates the basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 21 (a) shows a writing operation in the time interleaver and FIG.21(b) shows a reading operation in the time interleaver The firstXFECBLOCK is written column-wise into the first column of the TI memory,and the second XFECBLOCK is written into the next column, and so on asshown in (a). Then, in the interleaving array, cells are read outdiagonal-wise. During diagonal-wise reading from the first row(rightwards along the row beginning with the left-most column) to thelast row, N_(r) cells are read out as shown in (b). In detail, assumingz_(n,s,i) (i=0, . . . , N_(r)N_(o)) as the TI memory cell position to beread sequentially, the reading process in such an interleaving array isperformed by calculating the row index R_(n,s,i) the column indexC_(n,s,i), and the associated twisting parameter T_(n,s,i) as followsequation.

$\begin{matrix}{{{GENERATE}\left( {R_{n,s,i},C_{n,s,i}} \right)} = \left\{ {{R_{n,s,i} = {{mod}\left( {i,N_{r}} \right)}},{T_{n,s,i} = {{mod}\left( {{S_{shift} \times R_{n,s,i}},N_{c}} \right)}},{C_{n,s,i} = {{mod}\left( {{T_{n,s,i} + \left\lfloor \frac{i}{N_{r}} \right\rfloor},N_{c}} \right)}}} \right\}} & \left\lbrack {{Equation}\mspace{14mu} 8} \right\rbrack\end{matrix}$

where S_(shift) is a common shift value for the diagonal-wise readingprocess regardless of N_(xBLOCK_TI)(n, s), and it is determined byN_(xBLOCK_TI_MAX) given in the PLS2-STAT as follows equation.

$\begin{matrix}{{for}\left\{ {\begin{matrix}{{N_{{{xBLOCK}\_{TI}}{\_{MAX}}}^{\prime} = {N_{{{xBLOCK}\_{TI}}{\_{MAX}}} + 1}},} & {{{if}\mspace{14mu} N_{{{xBLOCK}\_{TI}}{\_{MAX}}}{mod}\; 2} = 0} \\{{N_{{{xBLOCK}\_{TI}}{\_{MAX}}}^{\prime} = N_{{{xBLOCK}\_{TI}}{\_{MAX}}}},} & {{{if}\mspace{14mu} N_{{{xBLOCK}\_{TI}}{\_{MAX}}}{mod}\; 2} = 1}\end{matrix},{S_{shift} = \frac{N_{{{xBLOCK}\_{TI}}{\_{MAX}}}^{\prime} - 1}{2}}} \right.} & \left\lbrack {{Equation}\mspace{14mu} 9} \right\rbrack\end{matrix}$

As a result, the cell positions to be read are calculated by acoordinate as z_(n,s,i)=N,C_(n,s,i)|R_(n,s,i).

FIG. 22 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 22 illustrates the interleaving array in the TImemory for each TI group, including virtual XFECBLOCKs whenN_(xBLOCK_TI)(0,0)=3, N_(xBLOCK_TI)(1,0)=6, N_(xBLOCK_TI)(2,0)=5.

The variable number N_(xBLOCK_TI)(n,s)=N, will be less than or equal toN′_(xBLOCK_TI_MAX). Thus, in order to achieve a single-memorydeinterleaving at the receiver side, regardless of N_(xBLOCK_TI)(n,s),the interleaving array for use in a twisted row-column block interleaveris set to the size of N_(r)×N_(c)=N_(cells)×N′_(xBlock_TI_MAX) byinserting the virtual XFECBLOCKs into the TI memory and the readingprocess is accomplished as follow equation.

[Equation 10] p = 0; for i = 0; i < N_(cells)N_(xBLOCK)_TI_MAX′; i = i +1 {GENERATE(R_(n,s,i), C_(n,s,i)); V_(i) = N_(r)C_(n,s,j) + R_(n,s,j) ifV_(i) < N_(cells)N_(xBLOCK)_TI(n,s) { Z_(n,s,p) = V_(i); p = p + 1; } }

The number of TI groups is set to 3. The option of time interleaver issignaled in the PLS2-STAT data by DP_TI_TYPE=‘0’, DP_FRAME_INTERVAL=‘1’,and DP_TI_LENGTH=1, i.e.,NTI=1, IJUMP=1, and PI=1. The number ofXFECBLOCKs, each of which has Ncells=30 cells, per TI group is signaledin the PLS2-DYN data by NxBLOCK_TI(0,0)=3, NxBLOCK_TI(1,0)=6, andNxBLOCK_TI(2,0)=5, respectively. The maximum number of XFECBLOCK issignaled in the PLS2-STAT data by NxBLOCK_Group_MAX, which leads to└N_(xBLOCK_Group_MAX)/N_(IT)┘=N_(xBLOCK_IT_MAX)=6.

FIG. 23 illustrates a diagonal-wise reading pattern of a twistedrow-column block interleaver according to an embodiment of the presentinvention.

More specifically FIG. 23 shows a diagonal-wise reading pattern fromeach interleaving array with parameters of N′_(xBLOCK_TI_MAX)=7 andSshift=(7−1)/2=3. Note that in the reading process shown as pseudocodeabove, if V_(i)≥N_(cells)N_(xBLOCK_TI)(n,s), the value of Vi is skippedand the next calculated value of Vi is used.

FIG. 24 illustrates interlaved XFECBLOCKs from each interleaving arrayaccording to an embodiment of the present invention.

FIG. 24 illustrates the interleaved XFECBLOCKs from each interleavingarray with parameters of N′_(xBLOCK_TI_MAX)=7 and S shift=3.

FIG. 25 is a diagram showing a protocol stack supporting a broadcastservice according to one embodiment of the present invention.

The broadcast service according to one embodiment of the presentinvention may provide not only audio/video (A/V) data but alsoadditional services such as an HTMLS application, an interactivityservice, an ACR service, a second screen service and a personalizationservice.

Such a broadcast service may be transmitted via a physical layer whichis a broadcast signal of a terrestrial wave, a satellite, etc. Inaddition, the broadcast service according to one embodiment of thepresent invention may be transmitted via an Internet communicationnetwork (broadband).

When the broadcast service is transmitted via the physical layer whichis the broadcast signal of the terrestrial wave, the satellite, etc., abroadcast reception device may demodulate a broadcast signal to extractan encapsulated MPEG-2 transport stream (TS) and an encapsulated IPdatagram. The broadcast reception device may extract a user datagramprotocol (UDP) datagram from the IP datagram. The broadcast receptiondevice may extract signaling information from the UDP datagram. At thistime, the signaling information may be in XML format. In addition, thebroadcast reception device may extract an asynchronous layeredcoding/layered coding transport (ALC/LCT) packet from the UDP datagram.The broadcast reception device may extract a file delivery overunidirectional transport (FLUTE) packet from the ALC/LCT packet. At thistime, the FLUTE packet may include real-time audio/video/subtitle data,non-real time (NRT) data and electronic service guide (ESG) data. Inaddition, the broadcast reception device may extract a real-timetransport protocol (RTCP) packet and an RTP control protocol (RTCP)packet from the UDP datagram. The broadcast reception device may extractA/V data and supplementary data from the real-time transport packet suchas the RTP/RTCP packet. At this time, at least one of the NRT data, theA/V data and the supplementary data may be in ISO base media file format(BMFF). In addition, the broadcast reception device may extractsignaling information such as NRT data, A/V or PSI/PSIP from the MPEG-2TS packet or the IP packet. At this time, the signaling information maybe in XML or binary format.

When the broadcast service is transmitted via the Internet communicationnetwork (broadband), the broadcast reception device may receive an IPpacket from the Internet communication network. The broadcast receptiondevice may extract a TCP packet from the IP packet. The broadcastreception device may extract an HTTP packet from the TCP packet. Thebroadcast reception device may extract A/V, supplementary data,signaling data, etc. from the HTTP packet. At this time, at least one ofthe A/V and the supplementary data may be in ISO BMFF. In addition, thesignaling information may be in XML format.

FIG. 26 is a diagram showing a transport layer of a broadcast serviceaccording to one embodiment of the present invention.

Transmission and reception of media content via the IP network accordingto one embodiment of the present invention is divided into transmissionand reception of a transport packet including actual media content andtransmission and reception of media content presentation information.The broadcast reception device 100 receives media content presentationinformation and receives a transport packet including media content. Atthis time, the media content presentation information indicatesinformation necessary for media content presentation. The media contentpresentation information may include at least one of spatial informationand temporal information necessary for media content presentation. Thebroadcast reception device 100 presents the media content based on themedia content presentation information.

In a detailed embodiment, the media content may be transmitted andreceived via the IP network according to the MMT standard. At this time,the content server 50 transmits a presentation information (PI) documentincluding the media content presentation information. In addition, thecontent server 50 transmits an MMT protocol (MMTP) packet includingmedia content according to a request of the broadcast reception device100. The broadcast reception device 100 receives a PI document. Thebroadcast reception device 100 receives a transport packet includingmedia content. The broadcast reception device 100 extracts the mediacontent from the transport packet including the media content. Thebroadcast reception device 100 presents the media content based on thePI document.

In another detailed embodiment, as in the embodiment of FIG. 26, themedia content may be transmitted and received via the IP networkaccording to the MPEG-DASH standard. In FIG. 26, the content server 50transmits a media presentation description (MPD) including the mediacontent presentation information. In a detailed embodiment, the MPD maybe transmitted by an external server other than the content server 50.The content server 50 transmits a segment including media contentaccording to a request of the broadcast reception device 100. Thebroadcast reception device 100 receives the MPD. The broadcast receptiondevice 100 requests the media content from the content server based onthe MPD. The broadcast reception device 100 receives the transportpacket including the media content according to the request. Thebroadcast reception device 100 presents the media content based on theMPD. The broadcast reception device 100 may include a DASH client in thecontroller 110. The DASH client may include an MPD parser for parsingthe MPD, a segment parser for parsing a segment, an HTTP client fortransmitting an HTTP request message and receiving an HTTP responsemessage via an IP transmitter/receiver 130 and a media engine forpresenting media.

FIG. 27 is a diagram showing the structure of a media presentationdescription (MPD) according to one embodiment of the present invention.The MPD may include a period element, an adaptation set element and arepresentation element.

The period element includes information on a period. The MPD may includeinformation on a plurality of periods. The period indicates aconsecutive time interval of media content presentation.

The adaptation set element includes information on an adaptation set.The MPD may include information on a plurality of adaptation sets. Theadaptation set is a set of media components including one or moreinterchangeable media content components. The adaptation set may includeone or more representations. Each adaptation set may include audio ofdifferent languages or subtitles of different languages.

The representation element includes information on a representation. TheMPD may include information on a plurality of representations. Therepresentation is a set of one or more media components and a pluralityof differently encoded representations may exist in the same mediacontent component. Meanwhile, if bitstream switching is possible, thebroadcast reception device 100 may switch from a received representationto another representation based on information updated during mediacontent presentation. In particular, the broadcast reception device 100may switch a received representation into another representationaccording to bandwidth environment. The representation may be dividedinto a plurality of segments.

The segment is a unit of media content data. The representation may betransmitted as a segment or a portion of a segment according to therequest of the media content receiver 30 using an HTTP GET or HTTPpartial GET method defined in HTTP 1.1 (RFC 2616).

In addition, the segment may include a plurality of sub segments. Thesub segment may mean a smallest unit indexed at a segment level. Thesegment may include an initialization segment, a media segment, an indexsegment, a bitstream switching segment, etc.

FIG. 28 is a diagram showing a transport layer of a broadcast serviceaccording to one embodiment of the present invention.

A broadcast transmission device 300 may transmit a broadcast service viaa broadcast signal composed of a plurality of layers. Among theplurality of layers for transmitting the broadcast service, a transportlayer for transmitting and receiving a raw broadcast signal via aphysical medium may be referred to as a physical layer. The broadcasttransmission device 300 may transmit a broadcast service and broadcastservice related data via one or more physical layer pipes (PLPs) overone or a plurality of frequencies. At this time, the PLP is a series oflogical data delivery paths capable of being identified on the physicallayer. The PLP may also be referred to as a data pipe. One broadcastservice may include a plurality of components. At this time, eachcomponent may be any one of audio, video and data components. Eachbroadcaster may transmit an encapsulated broadcast service via one or aplurality of PLPs using the broadcast transmission device 300. Morespecifically, the broadcaster may transmit a plurality of componentsincluded in one service through a plurality of PLPs using the broadcasttransmission device 300. Alternatively, the broadcaster may transmit aplurality of components included in one service via one PLP using thebroadcast transmission device 300. For example, in the embodiment ofFIG. 28, Broadcast #1 may transmit signaling information via one PLP(PLP #0) using the broadcast transmission device 300. In addition, inthe embodiment of FIG. 28, Broadcast #1 transmits Component 1 andComponent 2 included in a first broadcast service via different PLPs PLP#1 and PLP #2 using the broadcast transmission device 300. In theembodiment of FIG. 28, Broadcast # N transmits Component 1 and Component2 included in Services #1 via PLP # N. At this time, a real-timebroadcast service may be encapsulated into any one of IP, user datagramprotocol (UDP) and protocol for real-time content transmission, e.g.,real-time transport protocol (RTP). Even non-real-time content andnon-real-time data may be encapsulated into any one packet of an IP, auser datagram protocol (UDP) and a content transmission protocol, e.g.,FLUTE. Accordingly, the physical layer frame transmitted by thebroadcast transmission device 300 may include a plurality of PLPs fordelivering one or more components. Accordingly, the broadcast receptiondevice 100 should confirm all PLPs in order to scan the broadcastservice for acquiring broadcast service connection information.Therefore, there is a need for a broadcast transmission method and abroadcast reception method for enabling the broadcast reception device100 to efficiently scan the broadcast service.

FIG. 29 is a diagram showing the configuration of a broadcast receptiondevice according to one embodiment of the present invention.

In the embodiment of FIG. 29, the broadcast reception device 100includes a receiver 120 and a controller 150. The receiver 120 includesa broadcast receiver 110 and an Internet protocol (IP) communicationunit 130.

The broadcast receiver 110 includes a channel synchronizer 111, achannel equalizer 113 and a channel decoder 115.

The channel synchronizer 110 synchronizes a symbol frequency with timingin a manner that a broadcast signal received at baseband can be decoded.

The channel equalizer 113 compensates for distortion of the synchronizedbroadcast signal. More specifically, the channel equalizer 113compensates for distortion of the synchronized broadcast signal bymultipath, Dopper effect, etc.

The channel decoder 115 decodes the broadcast signal, distortion ofwhich is compensated for. More specifically, the channel decoder 115extracts a transport frame from the broadcast signal, distortion ofwhich is compensated for. At this time, the channel decoder 115 mayperform forward error correction (FEC).

The IP communication unit 130 receives and transmits data via anInternet network.

The controller 150 includes a signaling decoder 151, a transport packetinterface 153, a broadband packet interface 155, a baseband operationcontroller 157, a common protocol stack 159, a service map database 161,a service signaling channel processing buffer and parser 163, an A/Vprocessor 165, a broadcast service guide processor 167, an applicationprocessor 169 and a service guide database 171.

The signaling decoder 151 decodes the signaling data of the broadcastsignal.

The transport packet interface 153 extracts a transport packet from thebroadcast signal. At this time, the transport packet interface 153 mayextract data such as signaling information or an IP datagram from theextracted transport packet.

The broadband packet interface 155 extracts an IP packet from the datareceived from the Internet network. At this time, the broadband packetinterface 155 may extract signaling information or an IP datagram fromthe IP packet.

The baseband operation controller 157 controls operation related toreception of broadcast information from the baseband.

The common protocol stack 159 extracts audio or video from the transportpacket.

The A/V processor 547 processes audio or video.

The service signaling channel processing buffer and parser 163 parsesand buffers signaling information for signaling a broadcast service.More specifically, the service signaling channel processing buffer andparser 163 may parse and buffer signaling information for signaling thebroadcast service from the IP datagram.

The service map database 165 stores a broadcast service list includinginformation on broadcast services.

The service guide processor 167 processes terrestrial broadcast serviceguide data of the program of a terrestrial broadcast service.

The application processor 169 extracts and processes application relatedinformation from the broadcast signal.

The service guide database 171 stores program information of thebroadcast service.

FIGS. 30 to 31 are diagrams showing the configuration of a broadcastreception device according to another embodiment of the presentinvention.

In the embodiment of FIGS. 30 to 31, the broadcast reception device 100includes a broadcast receiver 110, an Internet protocol communicationunit 130 and a controller 150.

The broadcast receiver 110 may include a tuner 114, a physical frameparser 116 and a physical layer controller 118.

The tuner 114 receives a broadcast signal via a broadcast channel andextracts a physical frame. The physical frame is a transmission unit ofa physical layer. The physical frame parser 116 parses the receivedphysical frame and acquires a link layer frame.

The physical layer controller 118 controls operation of the tuner 114and the physical frame parser 116. In one embodiment, the physical layercontroller 118 may control the tuner 114 using RF information of thebroadcast channel. More specifically, when the physical layer controller118 transmits frequency information to the tuner 114, the tuner 114 mayacquire the physical frame corresponding to the received frequencyinformation from the broadcast signal.

In another embodiment, the physical layer controller 118 may controloperation of the physical layer parser 116 via the identifier of aphysical layer pipe. More specifically, the physical layer controller118 transmits identification information for identifying a specificphysical layer pipe among a plurality of physical layer pipesconfiguring the physical layer pipe to the physical frame parser 116.The physical frame parser 116 may identify the physical layer pipe basedon the received identification information and acquire a link layerframe from the identified physical layer pipe.

The controller 150 includes a link layer frame parser 164, an IP/UDPdatagram filter 171, a DTV control engine 174, an ALC/LCT+ client 172, atiming control unit 175, a DASH client 192, an ISO BMFF parser 194 and amedia decoder 195.

The link layer frame parser 164 extracts data from the link layer frame.More specifically, the link layer frame parser 164 may acquire linklayer signaling from the link layer frame. In addition, the link layerframe parser 164 may acquire an IP/UDP datagram from the link layerframe.

The IP/UDP datagram filter 171 filters a specific IP/UDP datagram fromthe IP/UDP datagram received from the link layer frame parser 164.

The ALC/LCT+ client 172 processes an application layer transport packet.The application layer transport packet may include an ALC/LCT+ packet.More specifically, the ALC/LCT+ client 172 may collect a plurality ofapplication layer transport packets and generate one or more ISO BMFFmedia file format objects.

The timing control unit 175 processes a packet including system timeinformation. The timing control unit 175 controls a system clockaccording to the processed result.

The DASH client 182 processes real-time streaming or adaptive mediastreaming. More specifically, the DASH client 192 may process adaptivemedia streaming based on the HTTP and acquires a DASH segment. At thistime, the DASH segment may be in the form of an ISO BMFF object.

The ISO BMFF parser 194 extracts audio/video data from the ISO BMFFobject received from the DASH client 192. At this time, the ISO BMFFparser 194 may extract audio/video data in access units. In addition,the ISO BMFF 194 may acquire timing information for audio/video from theISO BMFF object.

The media decoder 195 decodes the received audio and video data. Inaddition, the media decoder 195 presents the decoded result via a mediaoutput unit.

The DTV control engine 174 is an interface between modules. Morespecifically, the DTV control engine 174 may deliver parametersnecessary for operation of each module to control operation of eachmodule.

The Internet protocol communication unit 130 may include an HTTP accessclient 135. The HTTP access client 135 may transmit/receive a request ora response to the request to/from an HTTP server.

FIG. 32 is a diagram showing the configuration of a broadcast receptiondevice according to another embodiment of the present invention.

In the embodiment of FIG. 32, the broadcast reception device 100includes a broadcast receiver 110, an Internet protocol (IP)communication unit 130 and a controller 150.

The broadcast receiver 110 may include one or a plurality of processors,one or a plurality of circuits and one or a plurality of hardwaremodules for performing a plurality of functions performed by thebroadcast receiver 110. More specifically, the broadcast receiver 110may be a system on chip (SOC) in which several semiconductor parts areintegrated. At this time, the SOC may be a semiconductor device in whichvarious multimedia parts such as graphics, audio, video, modem, etc., aprocessor, and a semiconductor memory such as a DRAM are integrated. Thebroadcast receiver 110 may include a physical layer module 119 and aphysical layer IP frame module 117. The physical layer module 119receives and processes a broadcast related signal via a broadcastchannel of a broadcast network. The physical layer IP frame module 117converts a data packet of an IP datagram acquired from the physicallayer module 119 into a specific frame. For example, the physical layermodule 119 may convert the IP datagram, etc. into an RS frame, a GSE,etc.

The IP communication unit 130 may include one or a plurality ofprocessors, one or a plurality of circuits and one or a plurality ofhardware modules for performing a plurality of functions performed bythe IP communication unit 130. More specifically, the IP communicationunit 130 may be a system on chip (SOC) in which several semiconductorparts are integrated. At this time, the SOC may be a semiconductordevice in which various multimedia parts such as graphics, audio, video,modem, etc., a processor, and a semiconductor memory such as a DRAM areintegrated. The IP communication unit 130 may include an Internet accesscontrol module 131. The Internet access control module 131 controlsoperation of the broadcast reception device 100 for acquiring at leastone of a service, content and signaling data via an Internetcommunication network (broadband).

The controller 150 may include one or a plurality of processors, one ora plurality of circuits and one or a plurality of hardware modules forperforming a plurality of functions performed by the controller 150.More specifically, the controller 150 may be a system on chip (SOC) inwhich several semiconductor parts are integrated. At this time, the SOCmay be a semiconductor device in which various multimedia parts such asgraphics, audio, video, modem, etc., a processor, and a semiconductormemory such as a DRAM are integrated. The controller 150 may include atleast one of a signaling decoder 151, a service map database 161, aservice signaling channel parser 163, an application signaling parser166, an alert signaling parser 168, a targeting signaling parser 170, atargeting processor 173, an A/V processor 161, an alert processor 162,an application processor 169, a scheduled streaming decoder 181, a filedecoder 182, a user request streaming decoder 183, a file database 184,a component synchronizer 185, a service/content acquisition controller187, a redistribution module 189, a device manager 193 and a datasharing unit 191.

The service/content acquisition controller 187 controls operation of areceiver for acquiring a service, content and signaling data related tothe service or content acquired via the broadcast network or theInternet communication network.

The signaling decoder 151 decodes the signaling information.

The service signaling parser 163 parses the service signalinginformation.

The application signaling parser 166 extracts and parses the signalinginformation related to the service. At this time, the signalinginformation related to the service may be signaling information relatedto service scan. In addition, the signaling information related to theservice may be signaling information related to the content provided viathe service.

The alert signaling parser 168 extracts and parses the signalinginformation related to alert.

The targeting signaling parser 170 extracts and parses information forpersonalization of the service or content or information for signalingtargeting information.

The targeting processor 173 processes information for personalizing theservice content.

The alert processor 162 processes signaling information related toalert.

The application processor 169 controls execution of an application andapplication related information. More specifically, the applicationprocessor 169 processes the state of the downloaded application anddisplay parameters.

The A/V processor 161 processes operation related to rendering ofaudio/video based on the decoded audio or video, application data, etc.

The scheduled streaming decoder 181 decodes scheduled streaming which iscontent streamed according to the schedule previously decided by acontent provider such as a broadcaster.

The file decoder 182 decodes the decoded file. In particular, the filedecoder 182 decodes the file downloaded via the Internet communicationnetwork.

The user request streaming decoder 183 decodes content (on demandcontent) provided by a user request.

The file database 184 stores the file. More specifically, the filedatabase 184 may store the file downloaded via the Internetcommunication network.

The component synchronizer 185 synchronizes content or services. Morespecifically, the component synchronizer 185 synchronizes thepresentation time of the content acquired via at least one of thescheduled streaming decoder 181, the file decoder 182 and the userrequest streaming decoder 183.

The service/content acquisition controller 187 controls operation of thereceiver for acquiring at least one of a service, content and signalinginformation related to the service or content.

The redistribution module 189 performs operation for supportingacquisition of at least one of the service, content, information relatedto the service and information related to the content when the serviceor the content is not received via the broadcast network. Morespecifically, the redistribution module may request at least one of theservice, the content, the information related to the service and theinformation related to the content from an external management device300. At this time, the external management device 300 may be a contentserver.

The device manager 193 manages a connectable external device. Morespecifically, the device manager 193 may perform at least one ofaddition, deletion and update of the external device. In addition, theexternal device may be connected to and exchange data with the broadcastreception device 100.

The data sharing unit 191 may perform data transmission operationbetween the broadcast reception device 100 and the external device andprocesses exchange related information. More specifically, the datasharing unit 191 may transmit A/V data or signaling information to theexternal device. In addition, the data sharing unit 191 may receive A/Vdata or signaling information from the external device.

FIG. 33 is a diagram showing a broadcast transport frame according toone embodiment of the present invention.

In the embodiment of FIG. 33, the broadcast transport frame includes aP1 part, an L1 part, a common PLP part, an interleaved PLP (scheduled &interleaved PLP) part and an auxiliary data part.

In the embodiment of FIG. 33, the broadcast transmission devicetransmits information on transport signal detection via the P1 part ofthe broadcast transport frame. In addition, the broadcast transmissiondevice may transmit tuning information for broadcast signal tuning viathe P1 part.

In the embodiment of FIG. 33, the broadcast transmission devicetransmits the configuration of the broadcast transport frame and thecharacteristics of each PLP via the L1 part. At this time, the broadcastreception device 100 may decode the L1 part based on P1 and acquire theconfiguration of the broadcast transport frame and the characteristicsof each PLP.

In the embodiment of FIG. 33, the broadcast transmission device maytransmit information commonly applied to the PLPs via the common PLPpart. According to the detailed embodiment, the broadcast transmissionframe may not include the common PLP part.

In the embodiment of FIG. 33, the broadcast transmission devicetransmits a plurality of components included in a broadcast service viathe interleaved PLP part. At this time, the interleaved PLP partincludes a plurality of PLPs.

In the embodiment of FIG. 33, the broadcast transmission device maysignal information on through which PLP the component configuring thebroadcast service is signaled via the L1 part or the common PLP part.The broadcast reception device 100 should decode the plurality of PLPsof the interleaved PLP part in order to acquire the detailed broadcastservice information, for broadcast service scan.

Unlike the embodiment of FIG. 33, the broadcast transmission device maytransmit a broadcast transport frame including a separate part includinginformation on the component included in the broadcast service and thebroadcast service transmitted via the broadcast transport frame. At thistime, the broadcast reception device 100 may rapidly acquire thebroadcast service and information on the components included in thebroadcast service via a separate part. This will be described withreference to FIG. 32.

FIG. 34 is a diagram showing a broadcast transport frame according toanother embodiment of the present invention.

In the embodiment of FIG. 34, the broadcast transport frame includes aP1 part, an L1 part, a fast information channel (FIC) part, aninterleaved PLP (scheduled & interleaved PLP) part and an auxiliary datapart.

Parts other than the FIC_part are equal to those of the embodiment ofFIG. 33.

The broadcast transmission device transmits fast information via theFIC_part. The fast information may include configuration information ofthe broadcast stream transmitted via the transport frame, briefbroadcast service information and service signaling related to theservice/component. The broadcast reception device 100 may scan thebroadcast service based on the FIC_part. More specifically, thebroadcast reception device 100 may extract the information on thebroadcast service from the FIC_part.

FIG. 35 is a diagram showing the configuration of a transport packetaccording to one embodiment of the present invention. The transportpacket shown in FIG. 35 may use a transport protocol supporting reliabledata transmission. In a detailed embodiment, the reliable datatransmission protocol may be asynchronous layered coding (ALC). Inanother embodiment, the reliable data transmission protocol may belayered coding transport (LCT).

The packet header according to one embodiment of the present inventionmay include version information of the packet. More specifically, thepacket header may include version information of the transport packetwhich uses the transport protocol. In the embodiment, theabove-described information may be a V field. In addition, the V fieldmay have a size of 4 bits.

In addition, the packet header according to one embodiment of thepresent invention may include information associated with the length ofcongestion control information. More specifically, the packet header mayinclude the length of the congestion control information and informationon a multiple of the basic unit of the length of the congestion controlinformation.

In a detailed embodiment, the above-described information may be a Cfield. In one embodiment, the C field may be set to 0x00. In this case,the length of the congestion control information is 32 bits. In anotherembodiment, the C field may be set to 0x01. In this case, the length ofthe congestion control information may be 64 bits. In anotherembodiment, the C field may be set to 0x02. In this case, the length ofthe congestion control information may be 96 bits. In anotherembodiment, the C field may be set to 0x03. In this case, the length ofthe congestion control information may be 128 bits. The C field may havea size of 2 bits.

In addition, the packet header according to one embodiment may includeinformation specialized for the protocol. In a detailed embodiment, theabove-described information may be a PSI field. In addition, the PSIfield may have a size of 2 bits.

In addition, the packet header according to one embodiment of thepresent invention may include information associated with the length ofthe field indicating the identification information of the transportsession. More specifically, the packet header may include multipleinformation of the field indicating the identification information ofthe transport session. The above-described information may be an Sfield. The S field may have a size of 1 bit.

In addition, the packet header according to one embodiment of thepresent invention may include information associated with the length ofthe field indicating the identification information of the transportobject. More specifically, the packet header may include multipleinformation multiplied with the basic unit of the length of theidentification information of the transport object. The above-describedinformation may be an 0 field. The 0 field may have a size of 2 bits.

In addition, the packet header according to one embodiment of thepresent invention may include additional information associated with thelength of the field indicating the identification information of thetransport session. The packet header may include additional informationassociated with the length of the field indicating the identificationinformation of the transport object. The additional information may beinformation indicating whether half-word is added. Since the fieldindicating the identification information of the transport packet andthe field indicating the identification information of the transportobject should be present, the S field and the H field or the 0 field andthe H field may not simultaneously indicate 0 (zero).

In addition, the packet header according to one embodiment of thepresent invention may include information indicating that the session isfinished or is about to be finished. The above-described information maybe an A field. In a detailed embodiment, the A field may be set to 1 inorder to indicate that the session is finished or is about to befinished. Accordingly, generally, the A field may be set to 0. When thebroadcast transmission device sets the A field to 1, it is indicatedthat the last packet is being transmitted via the session. When the Afield is set to 1, the broadcast transmission device should maintain theA field to 1 until transmission of all packets following thecorresponding packet is finished. In addition, the broadcast receptiondevice may recognize that the broadcast transmission device is about tostop packet transmission via the session when the A field is set to 1.In other words, the broadcast reception device may recognize that packettransmission is no longer performed when the A field is set to 1. In oneembodiment, the A field may have a size of 1 bit.

In addition, the packet header according to one embodiment of thepresent invention may include information indicating that objecttransmission is finished or is about to be finished. The above-describedinformation may be a B field. In a detailed embodiment, the broadcasttransmission device may set the B field to 1 when object transmission isabout to be finished. Accordingly, generally, the B field may be set to0. When the information for identifying the transport object is notpresent in the transport packet, the B field may be set to 1. This mayindicate that transmission of the object in the session identified byout-of-band information is about to be finished. In addition, the Bfield may be set to 1 when the last packet for the object istransmitted. In addition, the B field may be set to 1 when the lastpacket for the object is transmitted for several seconds. The broadcasttransmission device should set the B field to 1 until transmission ofthe packet following the corresponding packet is finished, when the Bfield of the packet for a specific object is set to 1. The broadcastreception device 100 may recognize that the broadcast transmissiondevice will stop transmission of the packet for the object when the Bfield is set to 1. In other words, the broadcast reception device 100may recognize that the object is no longer transmitted via the session,from the B field set to 1. In one embodiment, the B field may have asize of 1 bit.

In addition, the packet header according to one embodiment of thepresent invention may include information indicating the total length ofthe header. The above-described information may be an HDR_LEN field. TheHDR_LEN field may be a multiple of 32 bits. In a detailed embodiment,when the HDR_LEN field is set to 5, the total length of the packetheader may be 160 bits which is a multiple of 32. In addition, theHDR_LEN field may be 8 bits.

In addition, the packet header according one embodiment of the presentinvention may include information related to encoding or decoding of thepayload included in the corresponding packet. The above-describedinformation may be referred to as a codepoint field. In one embodiment,the codepoint field may have a size of 8 bits.

In addition, the packet header according to one embodiment of thepresent invention may include congestion control information. Theabove-described information may be referred to as a congestion controlinformation (hereinafter, CCI) field. In a detailed embodiment, the CCIfield may include at least one of a current time slot index (CTSI)field, a channel number field and a packet sequence number field.

In addition, the packet header according to one embodiment of thepresent invention may include information for identifying the transportsession. The above-described information may be a transport sessionidentifier (hereinafter, TSI). In addition, the field in the packetheader including TSI information may be a TSI field.

In addition, the packet header according to one embodiment of thepresent invention may include information for identifying the objecttransmitted via the transport session. The above-described informationmay be a transport object identifier (hereinafter, TOI). In addition,the field in the packet header including the TOI information may be aTOI field.

In addition, the packet header according to one embodiment of thepresent invention may include information for transmitting additionalinformation. The above-described information may be referred to as aheader extension field. In one embodiment, the additional informationmay be time information related to presentation of the transport object.In another embodiment, the additional information may be timeinformation related to decoding of the transport object.

In addition, the transport packet according to one embodiment of thepresent invention may include payload identification information. In oneembodiment, the identification information may be payload identificationinformation associated with a forward error correction (FEC) scheme.Here, FEC is a type of the payload format defined in RFC 5109. The FECmay be used in the RTP or SRTP. The above-described information may bean FEC payload ID field.

In one embodiment, the FEC payload ID field may include information foridentifying the source block of the object. The above-describedinformation may be a source block number field. For example, when thesource block number field is set to N, the source block in the objectmay be numbered from 0 to N−1.

In another embodiment, the FEC payload ID field may include informationfor identifying a specific encoding symbol. The above-describedinformation may be an encoding ID field.

In addition, in one embodiment of the present invention, the transportpacket may include data in a payload. The field including theabove-described data may be an encoding symbol(s) field. In oneembodiment, the broadcast reception device 100 may extract the encodingsymbol(s) field and reconfigure the object. More specifically, the datain the encoding symbol(s) field may be generated from the source blocktransmitted via the packet payload.

FIG. 36 is a diagram showing the configuration of a service signalingmessage according to one embodiment of the present invention. Morespecifically, FIG. 36 shows the syntax of the service signaling messageheader according to one embodiment of the present invention. The servicesignaling message according to one embodiment of the present inventionmay include a signaling message header and a signaling message. At thistime, the signaling message may be represented in binary or XML format.In addition, the service signaling message may be included in thepayload of the transport protocol packet.

The signaling message header according to the embodiment of FIG. 36 mayinclude the identification information for identifying the signalingmessage. For example, the signaling message may be in the form of asection. In this case, the identification information of the signalingmessage may indicate the identifier (ID) of the signaling table section.The field indicating the identification information of the signalingmessage may be signaling_id. In a detailed embodiment, the signaling_idfield may have a size of 8 bits.

The signaling message header according to the embodiment of FIG. 36 mayinclude length information indicating the length of the signalingmessage. The field indicating the length information of the signalingmessage may be signaling_length. In a detailed embodiment, thesignaling_length field may have a size of 12 bits.

In addition, the signaling message header according to the embodiment ofFIG. 36 may include identifier extension information for extending theidentifier of the signaling message. At this time, the identifierextension information may be information for identifying signaling alongwith signaling identifier information. The field indicating theidentifier extension information of the signaling message may besignaling_id_extension.

At this time, the identifier extension information may include protocolversion information of the signaling message. The field indicating theprotocol version information of the signaling message may beprotocol_version. In a detailed embodiment, the protocol_version fieldmay have a size of 8 bits.

In addition, the signaling message header according to the embodiment ofFIG. 36 may include the version information of the signaling message.The version information of the signaling message may be changed when theinformation included in the signaling message is changed. The fieldindicating the version information of the signaling message may beversion number. In a detailed embodiment, the version number field mayhave a size of 5 bits.

In addition, the signaling message header according to the embodiment ofFIG. 36 may include information indicating whether the signaling messageis currently available. The field indicating whether the signalingmessage is available may be current next indicator. For example, whenthe current next indicator field is 1, the current next indicator fieldmay indicate that the signaling message is available. As anotherexample, when the current next indicator field is 0, thecurrent_next_indicator field may indicate that the signaling message isnot available and another signaling message including the same signalingidentification information, signaling identifier extension informationor fragment number information is available.

In addition, the signaling message header according to the embodiment ofFIG. 36 may include fragment number information of the signalingmessage. One signaling message may be divided into a plurality offragments and transmitted. Accordingly, information for identifying theplurality of fragments by the receiver may be fragment numberinformation. The field indicating the fragment number information may bea fragment_number field. In a detailed embodiment, the fragment_numberfield may have a size of 8 bits.

In addition, the signaling message header according to the embodiment ofFIG. 36 may include number information of a last fragment when onesignaling message is divided into a plurality of fragments. For example,when information on a last fragment number is 3, this indicates that thesignaling message is divided into three fragments. In addition, this mayindicate that the fragment including the fragment number of 3 includesthe last data of the signaling message. The field indicating the numberinformation of the last fragment may be last_fragment_number. In adetailed embodiment, the last_fragment_number field may have a size of 8bits.

FIG. 37 is a diagram showing the configuration of a service signalingmessage according to one embodiment of the present invention. Morespecifically, FIG. 37 shows the syntax of the service signaling messageheader according to one embodiment of the present invention. The servicesignaling message according to one embodiment of the present inventionmay include a signaling message header and a signaling message. At thistime, the signaling message may be represented in binary or XML format.In addition, the service signaling message may be included in thepayload of the transport protocol packet.

The signaling message header according to the embodiment of FIG. 37 mayinclude identifier information for identifying the signaling message.For example, the signaling message may be in the form of a section. Inthis case, the identifier information of the signaling message mayindicate the identifier (ID) of the signaling table section. The fieldindicating the identifier information of the signaling message may besignaling_id. In a detailed embodiment, the signaling_id field may havea size of 8 bits.

The signaling message header according to the embodiment of FIG. 37 mayinclude length information indicating the length of the signalingmessage. The field indicating the length information of the signalingmessage may be signaling_length. In a detailed embodiment, thesignaling_length field may have a size of 12 bits.

The signaling message header according to the embodiment of FIG. 37 mayhave identifier extension information for extending the identifier ofthe signaling message. At this time, the identifier extensioninformation may be information for identifying signaling along withsignaling identifier information. The field indicating the identifierextension information of the signaling message may besignaling_id_extension.

At this time, the identifier extension information may include protocolversion information of the signaling message. The field indicating theprotocol version information of the signaling message may beprotocol_version. In a detailed embodiment, the protocol_version fieldmay have a size of 8 bits.

In addition, the signaling message header according to the embodiment ofFIG. 37 may include the version information of the signaling message.The version information of the signaling message may be changed when theinformation included in the signaling message is changed. The fieldindicating the version information of the signaling message may beversion number. In a detailed embodiment, the version number field mayhave a size of 5 bits.

In addition, the signaling message header according to the embodiment ofFIG. 37 may include information indicating whether the signaling messageis currently available.

The field indicating whether the signaling message is available may becurrent_next_indicator. For example, when the current_next_indicatorfield is 1, the current_next_indicator field may indicate that thesignaling message is available. As another example, when thecurrent_next_indicator field is 0, the current_next_indicator field mayindicate that the signaling message is not available and anothersignaling message including the same signaling identificationinformation, signaling identifier extension information or fragmentnumber information is available.

In addition, the signaling message header according to the embodiment ofFIG. 37 may include the format information of the signaling messageincluded in the payload. As described above, the signaling message maybe represented in binary or XML format. In addition, the signalingmessage may be represented in other formats. Accordingly, the formatinformation may indicate the format of the signaling message included inthe payload and may indicate binary, XML, etc., for example. The fieldindicating the format information may be a payload_format field. In adetailed embodiment, the payload_format field may have a size of 2 bits.

In addition, the signaling message header according to the embodiment ofFIG. 37 may include valid time information of the signaling messageincluded in the payload. The valid time information of the signalingmessage may include information on the valid time of the signalingmessage. After the time defined in this field, the signaling message isno longer valid. The field indicating the valid time information may bean expiration field. In a detailed embodiment, the expiration field mayhave a size of 32 bits.

In addition, the signaling message header according to the embodiment ofFIG. 37 may include fragment number information of the signalingmessage. One signaling message may be divided into a plurality offragments and transmitted. Information for identifying the plurality offragments by the receiver may be fragment number information. The fieldindicating the fragment number information may be a fragment_numberfield. In a detailed embodiment, the fragment_number field may have asize of 8 bits.

In addition, the signaling message header according to the embodiment ofFIG. 37 may include number information of a last fragment when onesignaling message is divided into a plurality of fragments. For example,when information on a last fragment number is 3, this indicates that thesignaling message is divided into three fragments. In addition, this mayindicate that the fragment including the fragment number of 3 includesthe last data of the signaling message. The field indicating the numberinformation of the last fragment may be last_fragment_number. In adetailed embodiment, the last fragment_number field may have a size of 8bits.

FIG. 38 is a diagram showing the configuration of a broadcast servicesignaling message in a next generation broadcast system according to oneembodiment of the present invention. The broadcast service signalingmessage according to one embodiment is for a broadcast service signalingmethod for enabling the broadcast reception device 100 to receive atleast one of a broadcast service and content in the next generationbroadcast system.

The broadcast service signaling method according to the embodiment ofFIG. 38 may be based on the configuration of the signaling message shownin FIG. 36. The broadcast service signaling message according to theembodiment of FIG. 38 may be transmitted via a service signalingchannel. At this time, the service signaling channel may be a physicallayer pipe for directly transmitting the service signaling informationfor broadcast service scan without passing through other layers. In adetailed embodiment, the service signaling channel may be referred to asat least one of a fast information channel (FIC), low layer signaling(LLS) and an application layer transport session. The broadcast servicesignaling message according to the embodiment of FIG. 38 may be in anXML format.

The service signaling message according to the embodiment of FIG. 38 mayinclude information on the number of services included therein. Morespecifically, one service signaling message may include a plurality ofservices and include information on the number of services includedtherein. The information on the number of services may be a num_servicesfield. In a detailed embodiment, the num_services field may have a sizeof 8 bits.

In addition, the service signaling message according to the embodimentof FIG. 38 may include identifier information of the service. Theidentifier information may be a service_id field. In a detailedembodiment, the service_id field may have a size of 16 bits.

In addition, the service signaling message according to the embodimentof FIG. 38 may include service type information. The service typeinformation may be a service_type field. In a detailed embodiment, whenthe service_type field has a value of 0x00, the service type indicatedby the signaling message may be a scheduled audio service.

In another embodiment, when the service_type field has a value of 0x01,the service type indicated by the signaling message may be a scheduledaudio/video service. At this time, the scheduled audio/video service maybe an audio/video service broadcast according to a predeterminedschedule.

In another embodiment, when the service type field has a value of 0x02,the service type indicated by the signaling message may be an on-demandservice. At this time, the on-demand service may be an audio/videoservice presented by the request of the user. In addition, the on-demandservice may be a service having a concept opposed to that of thescheduled audio/video service.

In another embodiment, when the service type field has a value of 0x03,the service type indicated by the signaling message may be an app-basedservice. At this time, the app-based service is not a real-timebroadcast service but is a non-real-time service and is provided via anapplication. The app-based service may include at least one of a serviceassociated with a real-time broadcast service and a service notassociated with the real-time broadcast service. The broadcast receptiondevice 100 may download an application and provide an app-based service.

In another embodiment, when the service_type field has a value of 0×04,the service type indicated by the signaling message may be a rightsissuer service. At this time, the rights issuer service may be providedto only a person who has rights to receive a service.

In another embodiment, when the service_type field has a value of 0×05,the service type indicated by the signaling message may be a serviceguide service. At this time, the service guide service may provideinformation on a provided service. For example, the information on theprovided service may be a broadcast schedule.

In addition, the service signaling message according to the embodimentof FIG. 38 may include service name information. The service nameinformation may be a short_service_name field.

In addition, the service signaling message according to the embodimentof FIG. 38 may include length information of the short_service namefield. The length information of the short_service_name field may be ashort_service_name length field.

In addition, the service signaling message according to the embodimentof FIG. 38 may include may include broadcast service channel numberinformation associated with a service. The associated broadcast servicechannel number information may be a channel_number field.

In addition, the service signaling message according to the embodimentof FIG. 38 may include data necessary for the broadcast reception deviceto acquire a timebase or a signaling message according to the transportmode. The data necessary to acquire the timebase or the signalingmessage may be a bootstrap( ) field.

The transport mode may be at least one of a timebase transport mode anda signaling transmission mode. The timebase transport mode may be atransport mode for timebase including metadata on a timeline used for abroadcast service. The timeline is a series of time information formedia content. More specifically, the timeline may be a series ofreference times which is a media content presentation criterion.Information on the timebase transport mode may be atimebase_transport_mode field.

In addition, the signaling transmission mode may be a mode fortransmitting a signaling message used in a broadcast service. Theinformation on the signaling transport mode may be asignaling_transport_mode field.

FIG. 39 is a diagram showing the meaning of the value of atimebase_transport_mode field and a signaling_transport_mode field in aservice signaling message according to one embodiment of the presentinvention.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase of the broadcast service viaan IP datagram in the same broadcast stream. According to theembodiment, when the timebase_transport_mode field has a value of 0x00,the timebase_transport_mode field may indicate that the broadcastreception device may acquire the timebase of the broadcast service viathe IP datagram in the same broadcast stream.

In addition, the signaling transport mode may include a mode in whichthe broadcast reception device 100 acquires the signaling message usedfor the broadcast service via an IP datagram in the same broadcaststream. According to another embodiment, when the signalingtransport_mode field has a value of 0x00, the signaling_transport_modefield may indicate that the broadcast reception device acquires thesignaling message used for the broadcast service via the IP datagram inthe same broadcast stream. The same broadcast stream may mean the samebroadcast stream as the broadcast stream used for the broadcastreception device to receive the current service signaling message. Inaddition, the IP datagram may be a transport unit in which the componentconfiguring the broadcast service or content is encapsulated accordingto the Internet protocol. In this case, the bootstrap( ) field of thetimebase and the signaling message may follow the shown syntax. Theshown syntax may be represented in XML format.

FIG. 40 is a diagram showing the syntax of the bootstrap( ) field whenthe timebase_transport_mode field and the signaling_transport_mode fieldhave a value of 0x00 in one embodiment of the present invention.

In the embodiment, bootstrap data may include information on an IPaddress format of an IP datagram including the timebase or the signalingmessage. The information on the IP address format may be anIP_version_flag field. The information on the IP address format mayindicate that the IP address format of the IP datagram is IPv4. In oneembodiment, when the information on the IP address format is 0, theinformation on the IP address may indicate that the IP address format ofthe IP datagram is IPv4. The information on the IP address format mayindicate that the IP address format of the IP datagram is IPv6. In oneembodiment, when the information on the IP address format is 1, theinformation on the IP address may indicate that the IP address format ofthe IP datagram is IPv6.

In the embodiment, the bootstrap data may include information indicatingwhether the IP datagram including the timebase or the signaling messageincludes a source IP address. At this time, the source IP address may bea source address of the IP datagram. Information indicating whether theIP datagram includes the source IP address may be asource_IP_address_flag field. In one embodiment, when thesource_IP_address_flag field is 1, this may indicate that the IPdatagram includes the source IP address.

In the embodiment, the bootstrap data may include information indicatingwhether the IP datagram including the timebase or the signaling messageincludes a destination IP address. At this time, the destination IPaddress may be a destination address of the IP datagram. Informationindicating whether the IP datagram includes the destination IP addressmay be a destination_IP_address_flag field. In one embodiment, when thedestination_IP_address_flag field is 1, this may indicate that the IPdatagram includes the destination IP address.

In the embodiment, the bootstrap data may include source IP addressinformation of the IP datagram including the timebase or the signalingmessage. The source IP address information may be a source_IP_addressfield.

In the embodiment of FIG. 39, the bootstrap data may include destinationIP address information of the IP datagram including the timebase or thesignaling message. The destination IP address information may be adestination_IP_address field.

In the embodiment, the bootstrap data may include information on thenumber of flow ports of the IP datagram including the timebase or thesignaling message. At this time, the port may be a passage for receivingthe flow of the IP datagram. The information indicating the number ofuser datagram protocol (UDP) ports of the IP datagram may be aport_num_count field.

In the embodiment, the bootstrap data may include information on a userdata protocol (UDP) port number of the IP datagram including thetimebase or the signaling message. The user datagram protocol (UDP) is acommunication protocol for unidirectionally sending information via theInternet without exchanging information.

The description now returns to FIG. 39.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase of the broadcast service viathe IP datagram in a different broadcast stream. According to anotherembodiment of FIG. 39, when the timebase_transport_mode field has avalue of 0x01, the timebase_transport_mode field may indicate that thetimebase of the broadcast service is acquired via the IP datagram in thedifferent broadcast stream. The different broadcast stream may mean thebroadcast stream different from the broadcast stream for receiving thecurrent service signaling message.

In addition, the signaling transmission mode may include a mode in whichthe broadcast reception device 100 acquires the signaling message usedfor the broadcast service via the IP datagram in the different broadcaststream. According to another embodiment, when the signalingtransport_mode field has a value of 0x01, the signaling_transport_modefield may indicate that the signaling message used for the broadcastservice is acquired via the IP datagram in the different broadcaststream. In this case, the bootstrap( ) field of the timebase and thesignaling message may follow the syntax shown in FIG. 41. The syntaxshown in FIG. 41 may be represented in XML format.

The bootstrap data according to the embodiment of FIG. 41 may includeidentifier information of a broadcaster for transmitting the signalingmessage. More specifically, the bootstrap data may include uniqueidentifier information of a specific broadcaster for transmitting thesignaling message via a specific frequency or a transport frame. Theidentifier information of the broadcaster may be a broadcasting_idfield. In addition, the identifier information of the broadcaster may beidentifier information of the transport stream for transmitting thebroadcast service.

The description now returns to FIG. 39.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase via a session based flow inthe same broadcast stream.

According to another embodiment of FIG. 39, when thetimebase_transport_mode field has a value of 0x02, this may indicatethat the timebase of the broadcast service is acquired via the sessionbased flow in the same broadcast stream. The signaling transport modemay include a mode in which the broadcast reception device 100 acquiresthe signaling message via a session based flow in the same broadcaststream. The signaling transport mode may include a mode in which thebroadcast reception device 100 acquires the signaling message used forthe broadcast service via the session based flow in the same broadcaststream. When the signaling_transport_mode field has a value of 0x02,this may indicate that the signaling message used for the broadcastservice is acquired via the application layer transport session basedflow in the same broadcast stream. At this time, the application layertransport session based flow may be any one of an asynchronous layeredcoding (ALC)/layered coding transport (LCT) session and a file deliveryover unidirectional transport (FLUTE) session.

In this case, the bootstrap( ) field of the timebase and the signalingmessage may follow the syntax shown in FIG. 42. The syntax shown in FIG.42 may be represented in XML format.

The bootstrap data according to the embodiment of FIG. 42 may includetransport session identifier information of an application layer fortransmitting an application layer transport packet including thetimebase or the signaling message. At this time, the session fortransmitting the transport packet may be any one of an ALC/LCT sessionand a FLUTE session. The transport session identifier information of theapplication layer may be a tsi field.

The description now returns to FIG. 39.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase via a session based flow inthe different broadcast stream. According to another embodiment of FIG.39, when the timebase_transport_mode field has a value of 0x03, this mayindicate that the timebase of the broadcast service is acquired via thesession based flow in the different broadcast stream. The signalingtransport mode may include a mode in which the broadcast receptiondevice 100 acquires the signaling message via a session based flow inthe same broadcast stream. When the signaling_transport_mode field has avalue of 0x03, this may indicate that the signaling message used for thebroadcast service is acquired via the application layer transportsession based flow in the different broadcast stream. At this time, theapplication layer transport session based flow may be any one of anasynchronous layered coding (ALC)/layered coding transport (LCT) sessionand a file delivery over unidirectional transport (FLUTE) session.

In this case, the bootstrap( ) field of the timebase and the signalingmessage may follow the syntax shown in FIG. 43. The syntax shown in FIG.43 may be represented in XML format.

The bootstrap data according to the embodiment of FIG. 43 may includeidentifier information of a broadcaster for transmitting the signalingmessage. More specifically, the bootstrap data may include uniqueidentifier information of a specific broadcaster for transmitting thesignaling message via a specific frequency or a transport frame. Theidentifier information of the broadcaster may be a broadcasting_idfield. In addition, the identifier information of the broadcaster may beidentifier information of the transport stream of the broadcast service.

The description returns to FIG. 39.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase via a packet based flow inthe same broadcast stream. According to another embodiment of FIG. 39,when the timebase_transport_mode field has a value of 0×04, this mayindicate that the timebase of the broadcast service is acquired via thepacket based flow in the same broadcast stream. At this time, the packetbased flow may be an MPEG media transport (MMT) packet flow.

The signaling transport mode may include a mode in which the broadcastreception device 100 acquires the signaling message via the packet basedflow in the same broadcast stream. When the signaling_transport_modefield has a value of 0×04, this may indicate that the signaling messageused for the broadcast service is acquired via the transport packetbased flow in the same broadcast stream. At this time, the packet basedflow may be an MMT packet flow.

In this case, the bootstrap( ) field of the timebase and the signalingmessage may follow the syntax shown in FIG. 44. The syntax shown in FIG.44 may be represented in XML format.

The bootstrap data according to the embodiment of FIG. 44 may includeidentifier information of a transport packet for transmitting thetimebase or the signaling message. The identifier information of thetransport packet may be a packet_id field. The identifier information ofthe transport packet may be identifier information of the MPEG-2transport stream.

The description returns to FIG. 39.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase via a packet based flow inthe different broadcast stream.

According to another embodiment of FIG. 39, when thetimebase_transport_mode field has a value of 0×05, this may indicatethat the timebase of the broadcast service is acquired via the packetbased flow in the different broadcast stream. At this time, the packetbased flow may be an MPEG media transport packet flow.

The signaling transport mode may include a mode in which the broadcastreception device 100 acquires the signaling message via a packet basedflow in the different broadcast stream. When the signalingtransport_mode field has a value of 0×05, this may indicate that thesignaling message used for the broadcast service is acquired via thepacket based flow in the different broadcast stream. At this time, thepacket based flow may be an MMT packet flow.

In this case, the bootstrap( ) field of the timebase and the signalingmessage may follow the syntax shown in FIG. 45. The syntax shown in FIG.45 may be represented in XML format.

The bootstrap data according to the embodiment of FIG. 45 may includeidentifier information of a broadcaster for transmitting the signalingmessage. More specifically, the bootstrap data may include uniqueidentifier information of a specific broadcaster for transmitting thesignaling message via a specific frequency or a transport frame. Theidentifier information of the broadcaster may be a broadcasting_idfield. In addition, the identifier information of the broadcaster may beidentifier information of the transport stream of the broadcast service.

The bootstrap data according to the embodiment of FIG. 45 may includeidentifier information of a transport packet for transmitting thetimebase or the signaling message. The identifier information of thetransport packet may be a packet_id field. The identifier information ofthe transport packet may be identifier information of an MPEG-2transport stream.

The description returns to FIG. 39.

The timebase transport mode may include a mode in which the broadcastreception device 100 acquires the timebase via a URL.

According to another embodiment of FIG. 39, when thetimebase_transport_mode field has a value of 0×06, this may indicatethat the timebase of the broadcast service is acquired via the URL. Thesignaling transport mode may include a mode in which the broadcastreception device 100 acquires the signaling message via the URL. Whenthe signaling_transport_mode field has a value of 0×06, this mayindicate that the signaling message used for the broadcast service isacquired via the identifier for identifying the reception address of thesignaling message used for the broadcast service. At this time, theidentifier for identifying the reception address of the signalingmessage used for the broadcast service may be a URL.

In this case, the bootstrap( ) field of the timebase and the signalingmessage may follow the syntax shown in FIG. 46. The syntax shown in FIG.46 may be represented in XML format.

The bootstrap data according to the embodiment of FIG. 46 may includelength information of the URL where the timebase or the signalingmessage of the broadcast service is downloaded. The URL lengthinformation may be a URL_length field.

The bootstrap data according to the embodiment of FIG. 46 may includeactual data of the URL where the timebase or the signaling message ofthe broadcast service is downloaded. The actual data of the URL may be aURL_char field.

FIG. 47 is a diagram showing a process of acquiring a timebase and aservice signaling message in the embodiments of FIGS. 38 to 46.

As shown in FIG. 47, the broadcast reception device 100 according to oneembodiment of the present invention may acquire the timebase via apacket based transport protocol. More specifically, the broadcastreception device 100 may acquire the timebase via an IP/UDP flow using aservice signaling message. In addition, the broadcast reception device100 according to one embodiment of the present invention may acquire aservice related signaling message via a session based transportprotocol. More specifically, the broadcast reception device 100 mayacquire a service related signaling message via an ALC/LCT transportsession.

FIG. 48 is a diagram showing the configuration of a broadcast servicesignaling message in a next generation broadcast system according to oneembodiment of the present invention. The broadcast service signalingmessage according to one embodiment is for a service signaling methodfor enabling the broadcast reception device to receive a broadcastservice and content in the next generation broadcast system. Thebroadcast service signaling method according to the embodiment may bebased on the above-described signaling message configuration. Thebroadcast service signaling message according to the embodiment may betransmitted via a service signaling channel. At this time, the servicesignaling channel may be a physical layer pipe for directly transmittingthe service signaling information for broadcast service scan withoutpassing through other layers.

In a detailed embodiment, the signaling channel may be referred to as atleast one of a fast information channel (FIC), low layer signaling (LLS)and an application layer transport session. The broadcast servicesignaling message according to the embodiment may be represented in XMLformat.

The service signaling message according to the embodiment of FIG. 48 mayinclude information indicating whether the service signaling messageincludes information necessary to acquire the timebase. At this time,the timebase may include metadata on the timeline used for the broadcastservice. The timeline is a series of time information for media content.Information indicating whether information for acquiring the timebase isincluded may be a timeline_transport_flag field. In one embodiment, whenthe timeline_transport_flag field has a value of 1, this may indicatethat the service signaling message includes information for transmittingthe timeline.

The service signaling message according to the embodiment of FIG. 48 mayinclude data necessary for the broadcast reception device to acquire thetimeline or the signaling message according to the transport mode. Thedata for acquiring the timeline or the signaling message may be abootstrap_data( ) field.

The transport mode may be at least one of a timebase transport mode anda signaling transport mode. The timebase transport mode may be atransport mode for the timebase including metadata on the timeline usedfor the broadcast service. The information on the timebase transportmode may be a timebase_transport_mode field.

In addition, the signaling transport mode may be a mode for transmittingthe signaling message used for the broadcast service. The information onthe signaling transport mode may be a signaling_transport_mode field.

In addition, the meaning of the bootstrap data( ) field according to thetimeline_transport_mode field and the signaling_transport_mode field maybe equal to the above description.

FIG. 49 is a diagram showing the configuration of a broadcast servicesignaling message in a next generation broadcast system according to oneembodiment of the present invention. The broadcast service signalingmessage according to one embodiment is a service signaling method forenabling the broadcast reception device to receive a broadcast serviceand content in the next generation broadcast system. The broadcastservice signaling method according to the embodiment may be based on theabove-described signaling message configuration. The broadcast servicesignaling message according to the embodiment may be transmitted via aservice signaling channel. At this time, the service signaling channelmay be a physical layer pipe for directly transmitting the servicesignaling information for broadcast service scan without passing throughother layers. In a detailed embodiment, the signaling channel may bereferred to as at least one of a fast information channel (FIC), lowlayer signaling (LLS) and an application layer transport session. Thebroadcast service signaling message according to the embodiment of FIG.48 may be represented in XML format.

The service signaling message according to the embodiment may includeinformation indicating whether the service signaling message includesinformation necessary to acquire the timebase. At this time, thetimebase may include metadata on the timeline used for the broadcastservice. The timeline is a series of time information for media content.Information indicating whether information for acquiring the timebase isincluded may be a timeline_transport_flag field. In one embodiment, whenthe timeline_transport_flag field has a value of 1, this may indicatethat the service signaling message includes information for transmittingthe timeline.

The service signaling message according to the embodiment may includeinformation indicating whether the signaling message includes datanecessary to acquire the service signaling message. At this time, thesignaling message may be media presentation data (MPD) used for thebroadcast service or a signaling message related to an MPD URL. Theinformation indicating whether the information necessary to acquire thesignaling message is included may be an MPD_transport flag field. In oneembodiment, when the MPD_transport_flag field has a value of 1, this mayindicate that the service signaling message includes MPD or informationon transmission of the signaling message related to the MPD URL. HTTPbased adaptive media streaming may be referred to as dynamic adaptivestreaming over HTTP (DASH). In adaptive media streaming, detailedinformation for enabling the broadcast reception device to acquire thesegment configuring the broadcast service and content may be referred toas MPD. The MPD may be represented in XML format. The MPD URL relatedsignaling message may include address information capable of acquiringthe MPD.

In addition, the service signaling message according to the embodimentmay indicate whether the service signaling message includes acquisitionpath information of component data. At this time, the component may bethe unit of content data for providing the broadcast service. Theinformation indicating whether the acquisition path information of thecomponent data is included may be a component_location_transport_flagfield. In one embodiment, when the component_location_transport_flagfield has a value of 1, the component_location_transport_flag field mayindicate that the service signaling message includes the acquisitionpath information of the component data.

In addition, the service signaling message according to the embodimentmay indicate whether information necessary to acquire an applicationrelated signaling message is included. The information indicatingwhether the information necessary to acquire the application relatedsignaling message is included may be an app_signaling_transport_flagfield. In one embodiment, when the app_signaling_transport_flag fieldhas a value of 1, the app_signaling_transport_flag field may indicatethat the service signaling message includes acquisition path informationof the component data.

In addition, the service signaling message according to the embodimentmay indicate whether signaling message transmission related informationis included. The information indicating whether the signaling messagetransmission related information is included may be asignaling_transport_flag field. In one embodiment, when thesignaling_transport_flag field has a value of 1, thesignaling_transport_flag field may indicate that the service signalingmessage includes the signaling message transmission related information.When the service signaling message does not include the above-describedMPD related signaling, component acquisition path information andapplication related signaling information, the broadcast receptiondevice may acquire the MPD related signaling, component acquisition pathinformation and application related signaling information via thesignaling message transport path.

The service signaling message according to the embodiment may indicate amode for transmitting the timebase used for the broadcast service. Theinformation on the mode for transmitting the timebase may be atimebase_transport_mode field.

The service signaling message according to the embodiment may indicate amode for transmitting an MPD or MPD URL related signaling message usedfor the broadcast service. The information on the mode for transmittingan MPD or MPD URL related signaling message may be an MPD_transport_modefield.

The service signaling message according to the embodiment may indicate amode for transmitting a component location signaling message includingthe acquisition path of the component data used for the broadcastservice. The information on the mode for transmitting the componentlocation signaling message including the acquisition path of thecomponent data may be a component_location_transport_mode field.

The service signaling message according to the embodiment may indicate amode for transmitting an application related signaling message used forthe broadcast service. The information for transmitting the applicationrelated signaling message may be an app_signaling_transport_mode field.

The service signaling message according to the embodiment may indicate amode for transmitting a service related signaling message used for thebroadcast service. The information on the mode for transmitting theservice related signaling message may be a signaling_transport_modefield.

The meanings of the values of the timebase_transport_mode field, theMPD_transport_mode field, the component_location_transport_mode field,the app_signaling_transport_mode field and the signaling_transport_modefield will now be described.

FIG. 50 is a diagram showing the meaning of the value of each transportmode. The X_transport mode may include a timebase_transport_mode, anMPD_transport_mode, a component_location_transport_mode, anapp_signaling_transport_mode and a signaling_transport_mode. Thedetailed meaning of the value of each transport mode is equal to theabove description.

The service signaling message according to the embodiment of FIG. 49 mayinclude information necessary for the broadcast reception device toacquire the timeline or the signaling message according to the value ofeach mode. The information necessary to acquire the timebase or thesignaling message may be a bootstrap_data( ) field. More specifically,the information included in the bootstrap_data( ) is equal to the abovedescription.

FIG. 51 is a diagram showing the configuration of a signaling messagefor signaling a component data acquisition path of a broadcast servicein a next generation broadcast system. In the next generation broadcastsystem, one broadcast service may be composed of one or more components.Based on the signaling message according to the embodiment, thebroadcast reception device may acquire information on the acquisitionpath of the component data and related application in the broadcaststream. At this time, the signaling message according to the embodimentmay be represented in XML format.

The signaling message according to the embodiment may includeinformation indicating that the signaling message is a message forsignaling a component location. The information indicating that thesignaling message is the message for signaling the component locationmay be a signaling_id field. In a detailed embodiment, the signaling_idfield may have a size of 8 bits.

In addition, the signaling message according to the embodiment mayinclude extension information indicating that the signaling message is amessage for signaling a component location. At this time, the extensioninformation includes a protocol version of a message for signaling acomponent location. The extension information may be asignaling_id_extension field.

In addition, the signaling message according to the embodiment of FIG.50 may include version information of the message for signaling thecomponent location. At this time, the version information may indicatethat the information of the message for signaling the component locationhas been changed. The version information may be a version_number field.

In addition, the signaling message according to the embodiment mayinclude identifier information of an associated broadcast service. Atthis time, the identifier information of the associated broadcastservice may be a service_id field.

In addition, the signaling message according to the embodiment mayinclude the number of components associated with the broadcast service.At this time, the number of associated components may be a num_componentfield.

In addition, the signaling message according to the embodiment mayinclude the identifier of each component. For example, the componentidentifier may be configured by combining the MPD@id, period@id andrepresentation@id of MPEG DASH. At this time, the identifier informationof each component may be a component_id field.

In addition, the signaling message according to the embodiment mayinclude the length of the component_id field. At this time, the lengthinformation of the component_id field may be a component_id_lengthfield.

In addition, the signaling message according to the embodiment mayinclude frequency information indicating a frequency capable ofacquiring the component data. The component data may include a DASHsegment. At this time, the frequency information capable of acquiringthe component data may be a frequency_number field.

In addition, the signaling message according to the embodiment mayinclude a unique identifier of a broadcaster. The broadcaster maytransmit component data via a transmitted transport frame or a specificfrequency. At this time, the unique identifier information of thebroadcaster may be a broadcast_id field.

In addition, the signaling message according to the embodiment mayinclude the identifier of a physical layer pipe for transmittingcomponent data. At this time, the identifier information of the physicallayer pipe for transmitting the component data may be a datapipe_idfield.

In addition, the signaling message according to the embodiment mayinclude an IP address format of an IP datagram including component data.The information on the IP address format may be an IP_version_flagfield. The information on the IP address format of the IP datagram maybe an IP_version_flag field. In a detailed embodiment, when the value ofthe IP_version_flag field is 0, this may indicate IPv4 and, when thevalue of the IP_version_flag field is 1, this may indicate IPv6.

In addition, the signaling message according to the embodiment mayinclude information indicating whether the IP datagram including thecomponent data includes a source IP address. Information indicatingwhether the IP datagram includes the source IP address may be asource_IP_address_flag field. In one embodiment, when the sourceIP_address_flag field is 1, this may indicate that the IP datagramincludes the source IP address.

In addition, the signaling message according to the embodiment mayinclude information indicating whether the IP datagram including thecomponent data includes a destination IP address. Information indicatingwhether the IP datagram includes the destination IP address may be adestination_IP_address_flag field. In one embodiment, when thedestination_IP_address_flag field is 1, this may indicate that the IPdatagram includes the destination IP address.

In addition, the signaling message according to the embodiment mayinclude source IP address information of the IP datagram including thecomponent data. In one embodiment, when the source_IP_address_flag fieldhas a value of 1, the signaling message may include source IP addressinformation. The source IP address information may be asource_IP_address field.

In addition, the signaling message according to the embodiment mayinclude destination IP address information of the IP datagram includingthe component data. In one embodiment, when thedestination_IP_address_flag field has a value of 1, the signalingmessage may include destination IP address information. The destinationIP address information may be a destination_IP_address field.

In addition, the signaling message according to the embodiment mayinclude UDP port number information of the IP datagram including thecomponent data. The UDP port number information may be a UDP_port_numfield.

In addition, the signaling message according to the embodiment mayinclude transport session identifier information of the applicationlayer for transmitting the transport packet including the componentdata. The session for transmitting the transport packet may be at leastone of an ALC/LCT session and a FLUTE session. The identifierinformation of the session may be a tsi field.

In addition, the signaling message according to the embodiment mayinclude identifier information of the transport packet including thecomponent data. The identifier information of the transport packet maybe a packet_id field.

In addition, the signaling message according to the embodiment mayinclude the number of application signaling messages associated with thebroadcast service. At this time, the broadcast service may be identifiedaccording to the service_id field. The information on the number ofapplication signaling messages may be a num_app_signaling field.

In addition, the signaling message according to the embodiment mayinclude identifier information of the application signaling message. Theidentifier information of the application signaling message may be anapp_signaling_id field.

In addition, the signaling message according to the embodiment mayinclude length information of the app_signaling_id field. The lengthinformation of the app-signaling_id field may be anapp_signaling_id_length field.

In addition, the signaling message according to the embodiment mayinclude data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message. The information on thepath for acquiring the data of the application included in the signalingmessage associated with the identifier of the application signalingmessage may be an app_delivery-info( ) field.

FIG. 52 is a diagram showing the syntax of an app_delevery_info( ) fieldaccording to one embodiment of the present invention.

The data for the path capable of acquiring the data of the applicationincluded in the signaling message associated with the identifier of theapplication signaling message according to the embodiment may includeinformation indicating whether the application or associated data istransmitted via different broadcast streams. The information indicatingwhether the application or associated data is transmitted via differentbroadcast streams may be a broadcasting_flag field.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include the IP address format of the IP datagramincluding the application or associated data. The information on the IPaddress format of the IP datagram may be an IP_version_flag field. Inone embodiment, when the IP_version_flag field is 0, this may indicatethat the IP datagram including the application or associated data usesIPv4 and, when the IP_version_flag field is 1, this may indicate thatthe IP datagram including the application or associated data uses IPv6.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include information indicating whether the IP datagramincluding the application or associated data includes a source IPaddress. At this time, the associated data may be data necessary toexecute the application.

The information indicating whether the IP datagram including theapplication or associated data includes the source IP address may be asource_IP_address_flag field. In one embodiment, when thesource_IP_address_flag field is 1, this may indicate that the IPdatagram includes a source IP address.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include information indicating whether the IP datagramincluding the application or associated data includes a destination IPaddress. The information indicating whether the IP datagram includingthe application or associated data includes the destination IP addressmay be a destination_IP_address_flag field. In one embodiment, when thedestination_IP_address_flag field is 1, this may indicate that the IPdatagram includes a destination IP address.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include a unique identifier of a broadcaster fortransmitting the application or associated identifier.

In order words, the data for the path capable of acquiring the data ofthe application included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include the identifier of a broadcast service transportstream. The unique identifier information of the broadcaster fortransmitting the application or associated data via a transmittedtransport frame or a specific frequency may be a broadcast_id field.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include a source IP address of the IP datagram includingthe application or associated data, when the source_IP_address_flagfield has a value of 1. The source IP address information of the IPdatagram including the application or associated data may be asource_IP_address field.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include a destination IP address of the IP datagramincluding the application or associated data, when thedestination_IP_address_flag field has a value of 1. The destination IPaddress information of the IP datagram including the application orassociated data may be a destination_IP_address field.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include information on the number of flow ports of the IPdatagram including the application or associated data. The informationindicating the number of flow ports of the IP datagram including theapplication or associated data may be a port_num_count field.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include information on the UDP port number of the IPdatagram including the application or associated data. The informationon the UDP port number of the IP datagram including the application orassociated data may be a destination_UDP_port_number field.

In addition, the data for the path capable of acquiring the data of theapplication included in the signaling message associated with theidentifier of the application signaling message according to theembodiment may include the identifier of a transport session fortransmitting the application or associated data. The transport sessionfor transmitting the application or associated data may be any one of anALC/LCT session and a FLUTE session. The identifier information of thetransport session for transmitting the application or associated datamay be a tsi field.

FIG. 53 is a diagram showing the syntax of an app_delevery_info( ) fieldaccording to another embodiment of the present invention.

The data for the path capable of acquiring the data of the applicationincluded in the signaling message associated with the identifier of theapplication signaling message according to the embodiment may includethe identifier of the transport packet for transmitting the applicationor associated data. The transport packet for transmitting theapplication or associated data may follow a protocol based on a packetbased transport flow. For example, the packet based transport flow mayinclude an MPEG media transport protocol. The identifier information ofthe transport packet for transmitting the application or associated datamay be a packet_id field.

FIG. 54 is a diagram showing component location signaling including pathinformation capable of acquiring one or more component data configuringa broadcast service. More specifically, FIG. 54 shows information on apath capable of acquiring component data including a DASH segment whenone or more components configuring the broadcast service are representedby the DASH segment.

FIG. 55 is a diagram showing the configuration of the component locationsignaling of FIG. 54.

The component location signaling according to the embodiment may includeidentifier information of the MPEG DASH MPD associated with thebroadcast service. The identifier information of the MPEG DASH MPD maybe an mpdip field.

In addition, the component location signaling according to theembodiment may include the identifier of period attributes in the MPEGDASH MPD. The identifier information of the period attributes in theMPEG DASH MPD may be a periodid field.

In addition, the component location signaling according to theembodiment may include the identifier of representation attributes inthe period indicated by the periodid field. The identifier informationof the representation attributes in the period may be a ReptnlD field.

In addition, the component location signaling according to theembodiment may include a frequency number capable of acquiring the DASHsegment included in the representation attributes in the periodindicated by the ReptnlD field. The frequency number capable ofacquiring the DASH segment may be an RF channel number. The informationon the frequency number capable of acquiring the DASH segment may be anRFChan field.

In addition, the component location signaling according to theembodiment may include the unique identifier of the broadcaster fortransmitting the DASH segment through a specific frequency or atransmitted transport frame. The information on the unique identifier ofthe broadcaster for transmitting the DASH segment may be aBroadcastingid field.

In addition, the component location signaling according to theembodiment may include the identifier of the physical layer pipe fordelivering the DASH segment. The physical layer pipe may be a data pipetransmitted via the physical layer. The information on the identifier ofthe physical layer pipe for delivering the DASH segment may be aDataPipeId field.

In addition, the component location signaling according to theembodiment may include the destination IP address of the IP datagramincluding the DASH segment. The destination IP address information ofthe IP datagram including the DASH segment may be an IPAdd field.

In addition, the component location signaling according to theembodiment may include the UDP port number of the IP datagram includingthe DASH segment. The information on the UDP port number of the IPdatagram including the DASH segment may be a UDPPort field.

In addition, the component location signaling according to theembodiment may include the identifier of the transport session fortransmitting the transport packet including the DASH segment. Theidentifier of the session for transmitting the transport packet may beat least one of the ALC/LCT session and the FLUTE session. Theinformation on the identifier of the session for transmitting thetransport packet may be a TSI field.

In addition, the component location signaling according to theembodiment may include the identifier of the transport packet includingthe DASH segment. The information on the identifier of the transportpacket may be a Packetld field.

FIG. 56 is a diagram showing other information included in signaling ofa broadcast service in a next generation broadcast system in oneembodiment of the present invention. The signaling of the service mayinclude information on a service identifier (id), a service type, aservice name, a channel number, a timebase location, a delivery mode,bootstrap info, MPD, an MPD signaling location, a component signalinglocation, an app signaling location and/or an object flow.

The service identifier may indicate information for identifying theservice and may be expressed by id attributes.

The service type information may indicate the type of the service andmay be expressed by serviceType attributes.

The service name information may indicate the name of the service andmay be expressed by serviceName attributes.

The channel number information may indicate information on the channelnumber related to the service and may be expressed by channelNumberattributes.

The timebase location information may indicate the location where thetimebase can be acquired and may be expressed by a TimebaseLocationelement. Here, the timebase may indicate information indicating metadatato establish the timeline for synchronizing the components included inthe service.

The delivery mode information included in the timebase locationinformation may indicate the delivery mode of the timebase.

The bootstrap information included in the timebase location informationmay include the bootstrap information of the timebase according to thedelivery mode.

The MPD may indicate the MPD associated with the service.

The MPD signaling location information may indicate the location wheresignaling related to the MPD or MPD URL can be acquired.

The delivery mode information included in the MPD signaling location mayindicate the delivery mode of the MPD location signaling.

The bootstrap info information included in the MPD signaling locationmay include the bootstrap information of the MPD or the MPD URLaccording to the delivery mode.

The component signaling location information may indicate componentlocation signaling information associated with the service.

The delivery mode information included in the component signalinglocation information may indicate the delivery mode of the componentlocation signaling.

The bootstrap info information included in the component signalinglocation information may include the bootstrap information of thecomponent location signaling according to the delivery mode.

The app signaling location information may indicate the location wherethe application signaling can be acquired.

The delivery mode information included in the app signaling locationinformation may indicate the delivery mode of the application signaling.

The bootstrap info information included in the app signaling locationinformation may include the bootstrap information of the applicationsignaling according to the delivery mode.

The object flow information may include information on the relatedobject flows for transmitting the components of the service.

FIG. 57 is a diagram showing a delivery mode included in servicesignaling of a next generation broadcast system according to oneembodiment of the present invention.

As described above, the delivery mode may be included in each locationelement as attributes. The delivery mode may be distinguished as followsaccording to the value thereof.

When the value of the delivery mode is 0x00, this may indicate thatIPv4/IPv6 flows are transmitted through the same broadcast or cellularnetwork as the broadcast stream for receiving the service signalingmessage.

When the value of the delivery mode is 0x01, this may indicate thatIPv4/IPv6 flows are transmitted through different broadcast networks.

When the value of the delivery mode is 0x02, this may indicate thatsession-based flows may be transmitted through the same broadcastnetwork. Here, the session-based flow may mean an ALC/LCT or FLUTEsession according to the embodiment.

When the value of the delivery mode is 0x03, this may indicate thatsession-based flows may be transmitted through different broadcastnetworks. Here, the session-based flow may mean an ALC/LCT or FLUTEsession according to the embodiment.

When the value of the delivery mode is 0×04, this may indicate thatpacket-based flows may be transmitted through the same broadcastnetwork. Here, the packet-based flow may mean MMT packet basedtransmission according to the embodiment.

When the value of the delivery mode is 0x05, this may indicate thatpacket-based flows may be transmitted through different broadcastnetworks. Here, the packet-based flow may mean MMT packet basedtransmission according to the embodiment.

When the value of the delivery mode is 0×06, this may indicate that thelocation is designated by the URL.

The values 0×07 to 0xFF of the delivery mode are not set and are used toindicate the other delivery modes.

As described above, the information included in the timebase location,the MPD signaling location, the component signaling location and the appsignaling location element may be transmitted via the path equal to ordifferent from that of the service signaling according to the deliverymode.

FIG. 58 is a diagram showing information on a bootstrap included inservice signaling of a next generation broadcast system according to oneembodiment of the present invention. The information on the bootstrapmay be expressed by the Bootstrapinfo element as follows.

The BootstrapInfo element described in the above-described signalingmessage may include information for enabling a receiver to acquiretimebase information, MPD or MPD URL information, component signalinginformation, application signaling information, etc. That is, asdescribed above, the BootstrapInfo may be included in each locationelement. Therefore, the BootstrapInfo element may include information onan IP address, a port number, a transport session identifier and/or anassociated packet identifier.

More specifically, the BootstrapInfo element may include attributes suchas RFchannel, broadcastID, datapipeID (PLPID), sourceIP, desitinationIP,destinationPort, tsi, URL, packetid, etc. The information included inthe BootstrapInfo element may be changed according to the delivery modeincluded in the location element to which the BootstrapInfo elementbelongs.

The RFchannel attribute may include information on a radio frequencychannel carrying a broadcast stream.

The broadcastID attribute may indicate the identifier of the broadcasterfor transmitting the broadcast stream.

The datapipeID (PLPID) attribute may indicate the identifier of thephysical layer data pipe carrying IP datagrams. The datapipeID may beexpressed by PLPID and the PLPID may indicate the identifier of thephysical layer pipe.

The sourceIP attribute may indicate the source address of the IPdatagrams carrying associated data.

The destinationIP attribute may indicate the destination address of theIP datagrams carrying associated data.

The destinationPort attribute may indicate the destination port numberof the IP datagrams carrying associated data.

The tsi attribute may indicate the identifier of the transport sessionfor delivering transport packets carrying associated data.

The URL attribute may indicate the URL where associated data can beacquired.

The packetid attribute may indicate the identifier of the transportpackets carrying associated data.

Hereinafter, the objectFlow element of the information included in thesignaling for the broadcast service shown in FIG. 56 will be describedwith reference to FIG. 59.

FIG. 59 is a diagram showing information included in signaling for anobject flow. Each object flow may be a flow for transmitting one or morecomponents configuring the service. Therefore, one service may includeinformation on one or more object flows.

The object flow may include id, objectFormat, contentType and/orcontentEncoding attributes. In addition, the object flow may include afile element and the file element may include contentLocation and/or TOIattributes. In addition, the object flow may include a FileTemplateelement and the FileTemplate element may include contentLocTemplate,startTOI, endTOI and/or scale attributes. In addition, the object flowmay include an ObjectGroup element and the ObjectGroup element mayinclude contentLocation, startTOI and/or end TOI attributes. Inaddition, the object flow may include the above-described BootstrapInfoelement.

The id may indicate the identifier of the object flow. When the DASHsegment is delivered via this object flow, the id can be equal to acombination of the MPD identifier, the period identifier and the DASHrepresentation identifier.

The objectFormat may indicate the format of the objects in this objectflow as described above.

The contentType may indicate the media content component type for thisobject flow.

The contentEncoding may indicate the encoding method of the objectsdelivered via this object flow.

The file element may include information on the file.

The contentLocation of the file element may indicate the location wherethe file can be acquired. When the DASH segment is delivered via thisobject flow, the contentLocation may be equal to the DASH segment URL.

The TOI attribute of the file element is a transport object identifierand may indicate the identifier of the transport object.

The FileTemplate element may include information on a file template.

The contentLocTemplate of the FileTemplate element may indicate thetemplate used to generate the location where the file can be acquired.

The startTOI of the FileTemplate element may indicate a first TOIdelivered via this object flow.

The endTOI of the FileTemplate element may indicate a last TOI deliveredvia this object flow.

The scale attribute of the FileTemplate element may indicate informationon the scale between TIO values in this object flow.

The ObjectGroup element may include information on the group of thetransport objects delivered via this object flow.

The contentLocation of the ObjectGroup element may indicate the locationof the content associated with this object group.

The startTOI of the ObjectGroup element may indicate a first TOIdelivered via this object group.

The endTOI of the ObjectGroup element may indicate a last TOI deliveredvia this object group.

The BootstrapInfo element may include the bootstrap information of thisobject flow.

The objectFormat attributes of the information included in the signalingfor the object flow according to the embodiment of FIG. 59 may includeinformation on the format of the payload included in this objectdelivered via the object flow. In a first embodiment, the object formatattributes of the object flow may indicate that the payload included inthe flow includes a generic file supporting real-time streaming. Theobject format according to the first embodiment may be a generic file.

In a second embodiment, the object format attributes of the object flowmay indicate that the payload included in the flow includes a data filesupporting real-time streaming. For example, the object formatattributes according to the second embodiment may indicate the DASHsegment in the ISOBMFF. In a third embodiment, the object formatattributes of the object flow may indicate that the payload included inthe flow includes a data file represented in the HTTP entity format inorder to support real-time streaming. The HTTP entity may be one entityfor transmitting content according to HTTP.

Hereinafter, the File Template element of the information included inthe signaling for the object flow shown in FIG. 59 will be describedwith reference to FIG. 60.

FIG. 60 is a diagram showing a combination of information forrepresenting a file template in one embodiment of the present invention.The file template may be represented by a combination ofRepresentation@id and segment number. For example, when the DASH segmentis transmitted, as shown in FIG. 60, Representation@id and segmentnumber may be combined to dynamically generate information on thecontent location of each file. As a result, the broadcast receptiondevice can efficiently acquire the flow of the transport packetsincluding a specific component according to the dynamically generatedcontent location information.

FIG. 61 is a diagram showing an object flow included in servicesignaling according to one embodiment of the present invention.

The object flow may further include a default attribute @isDefault alongwith the object format attributes described with reference to FIG. 59.That is, the object flow may include id, objectFormat, contentType,contentEncoding and/or isDefault attributes. In addition, the objectflow may include a File element and the File element may includecontentLocation and/or TOI attributes. The object flow may include aFileTemplate element and the FileTemplate element may includecontentLocTemplate, startTOI, endTOI and/or scale attributes. Inaddition, the object flow may include an ObjectGroup element and theObjectGroup element may include contentLocation, startTOI and/or endTOIattributes. In addition, the object flow may include the above-describedBootstrapinfo element.

The id may indicate the identifier of this object flow. When the DASHsegment is delivered via this object flow, the id can be equal to acombination of the MPD identifier, the period identifier and the DASHrepresentation identifier.

The objectFormat may indicate the format of the objects in this objectflow as described above.

The contentType may indicate the media content component type for thisobject flow.

The contentEncoding may indicate the encoding method of the objectsdelivered via this object flow.

The isDefault may indicate whether the payload included in the objectdelivered via the object flow includes component data used by default.For example, this may indicate whether the receiver basically receivesand represents the component data delivered via this object flow withoutreceiving and processing additional signaling information such as DASHMPD.

The file element may include information on the file.

The contentLocation of the file element may indicate the location wherethe file can be acquired. When the DASH segment is delivered via thisobject flow, the contentLocation may be equal to the DASH segment URL.

The TOI attribute of the file element is a transport object identifierand may indicate the identifier of the transport object.

The FileTemplate element may include information on a file template.

The contentLocTemplate of the FileTemplate element may indicate thetemplate used to generate the location where the file can be acquired.

The startTOI of the FileTemplate element may indicate a first TOIdelivered via this object flow.

The endTOI of the FileTemplate element may indicate a last TOI deliveredvia this object flow.

The scale attribute of the FileTemplate element may indicate informationon the scale between TOI values in this object flow.

The ObjectGroup element may include information on the group oftransport objects delivered via this object flow.

The contentLocation of the ObjectGroup element may indicate the locationof the content associated with this object group.

The startTOI of the ObjectGroup element may indicate a first TOIdelivered via this object group.

The endTOI of the ObjectGroup element may indicate a last TOI deliveredvia this object group.

The BootstrapInfo element may include the bootstrap information of thisobject flow.

FIG. 62 is a diagram showing other information included in signaling ofa broadcast service in a next generation broadcast system in oneembodiment of the present invention. An existing FLUTE client mayreceive a file description table (FDT) and then a broadcast receptiondevice may receive a file according to the FDT. However, this method isnot suitable for transmission and reception of the file via thereal-time broadcast service. In other words, the FLUTE protocol may notbe suitably applied to the real-time broadcast service using aunidirectional transport protocol. Accordingly, in one embodiment of thepresent invention, the service signaling may include FDT information.

More specifically, as shown in FIG. 62, the FDTInstance elementaccording to one embodiment of the present invention may include an @idattribute (element). The @id attribute may indicate the specificidentifier of the FDT instance. Accordingly, the broadcast receptiondevice may identify the FDT instance via the @id attribute todynamically generate the FDT instance. In addition, the broadcastreception device may receive and process real-time streaming datarepresented in the form of the file according to the generated FDTinstance (The other attributes should be described).

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Expires attribute. The @Expiresattribute may include information on the expiration information of theFDTInstance. Accordingly, the broadcast reception device 100 may discardthe expired FDTInstance according to the @Expires attribute.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Complete attribute. In one embodiment,when the @Complete attribute has a true value, the @Complete attributemay indicate that the future FDTInstance to be provided in the samesession does not include new data.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Content-Location attribute. The@Content-Location attribute may be assigned a valid URI.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @TOI attribute. The @TOI attribute isnecessarily assigned a valid TOI value.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Content-Length attribute. The@Content-Length attribute may be the actual length information of thefile content.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Transfer-Length attribute. The@Transfer-Length attribute may be the transfer length of file content.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Content-Encoding attribute. The@Content-Encoding attribute may be encoding information of file content.

In addition, the FDTInstance element according to one embodiment of thepresent invention may include an @Content-Type attribute. The@Content-Type attribute may be type information of file content.

FIG. 63 is a diagram showing signaling information for transport sessioninformation of a session level according to one embodiment of thepresent invention. When real-time or non-real-time content istransmitted using an LCT based protocol, signaling informationdescribing the transport session information of a session level, such asa TSID, may be used. The TSID may be transmitted via some of thesignaling message using various methods such as an in-band method oftransport content or an out-of-band method using a separate path.

The TSID is an abbreviation for transport session instance descriptorand may indicate a descriptor including detailed information on thetransport session.

The TSID may include a tsi attribute, a PayloadFormat elementtransmitted via a SourceFlow and/or a RepairFlow. In addition, thePayloadFormat element may include codePoint, protocol,deliveryObjectFormat, realtime, isobmff and/or packetheadersizeattributes. In addition, the PayloadFormat element may include EFIDand/or ApplicationIdentifier elements.

The tsi may indicate a transport session identifier.

The codePoint may define what code point value is used for this payload.This value may indicate the value of the CP field of the LCT header.

The protocol indicates the transport protocol of this payload. That is,the protocol may define the transport protocol of each payload at apayload level. Various types may exist in the LCT based transportprotocol and the type may be identified by assigning an integer value toeach type. For example, 0 may identify the ALC and 1 may identify ROUTE.In addition, the same identification method is applicable to the otherprotocols and new protocols to be defined in the future. In addition, inthe above-described embodiment, the other @protocol value may beassigned in units of the LCT packet having the codepoint value equal tothe value assigned to the @codepoint to transmit content using variousprotocols within one transport session.

The deliveryObjectFormat may indicate the payload format of thetransport object.

The realtime may indicate whether the LCT packet includes component datafor a real-time service. When the component data for the real-timeservice is included, this may indicate whether an extension headerincluding NTP timestamps representing the presentation time of thetransport object is included.

The isobmff may indicate whether the transport object is a sequence ofISOBMFF boxes, a DASH object referred to by the MPD or a sequence ofISOBMFF boxes fragmented according to a MPU mode of an MMT.

The packetheadersize may indicate the size of the route packet header.

The EFID may include detailed information of file delivered data.

The ApplicationIdentifier may provide additional information which canbe mapped to the application which is carried in this transport session,e.g., the RepresentationID of the DASH content.

FIG. 64 is a diagram showing signaling information for transport sessioninformation of a session level according to another embodiment of thepresent invention. When real-time or non-real-time content istransmitted using an LCT based protocol, signaling informationdescribing the transport session information of a session level, such asa TSID, may be used. The TSID may be transmitted via some of thesignaling message using various methods such as an in-band method oftransport content or an out-of-band method using a separate path.

When the protocols of the packets transmitted within one transportsession are all identical, the TSID may have the following structure.That is, a protocol attribute may exist at TransportSession protocolattribute and may indicate that all packets of the session having theTSI value of the tsi attribute are transmitted via the protocolcorresponding to the value assigned to the protocol attribute.

The TSID may include a tsi attribute, a protocol attribute of aSourceFlow, a PayloadFormat element and/or a RepairFlow of eachtransport session. In addition, the PayloadFormat element may includecodePoint, deliveryObjectFormat, realtime, isobmff and/orpacketheadersize attributes. In addition, the PayloadFormat element mayinclude EFID and/or ApplicationIdentifier elements.

The tsi may indicate a transport session identifier.

The protocol indicates the transport protocol of this payload. Varioustypes may exist in the LCT based transport protocol and the type may beidentified by assigning an integer value to each type. For example, 0may identify the ALC and 1 may identify ROUTE. In addition, the sameidentification method is applicable to the other protocols and newprotocols to be defined in the future. In addition, in theabove-described embodiment, content transmission using the same protocolis possible with respect to all the packets included in one transportsession.

The codePoint may define what code point value is used for this payload.This value may indicate the value of the CP field of the LCT header.

The deliveryObjectFormat may indicate the payload format of thetransport object.

The realtime may indicate whether the LCT packet includes an extensionheader including NTP timestamps representing the presentation time ofthe transport object.

The isobmff may indicate whether the transport object is a sequence ofISOBMFF boxes, a DASH object referred to by the MPD or a sequence ofISOBMFF boxes fragmented according to a MPU mode of an MMT.

The packetheadersize may indicate the size of the route packet header.

The EFID may include detailed information of file delivered data.

The ApplicationIdentifier may provide additional information which canbe mapped to the application which is carried in this transport session,e.g., the RepresentationID of the DASH content.

FIG. 65 is a flowchart illustrating a process of operating a broadcastreception device according to one embodiment of the present invention.

A reception unit of the broadcast reception device receives a transportprotocol packet including a service signaling message (S101). Thereception unit may include an Internet protocol communication unit and abroadcast reception unit. The service signaling message may beinformation for signaling at least one of a broadcast service and mediacontent. In one embodiment, the transport protocol may be an Internetprotocol (IP). In addition, in one embodiment, the service signalingmessage may be expressed in at least one of binary format and XMLformat. The transport protocol packet may include a signaling messageheader and a signaling message.

A controller of the broadcast reception device extracts the servicesignaling message from the received transport protocol packet (S103).More specifically, the transport protocol packet may be parsed toextract the service signaling message. The controller may acquire anInternet protocol datagram from the layered transport protocol packet.The acquired Internet protocol datagram may include the servicesignaling message.

The controller of the broadcast reception device acquires informationfor providing a broadcast service from the service signaling message(S105). The information for providing the broadcast service may be partof the service signaling message.

In one embodiment, the information for providing the broadcast servicemay be service information for a timebase including metadata on atimeline which is a series of time information for content.

In another embodiment, information for providing a broadcast service maybe service information of detailed information for acquisition ofsegments configuring content in adaptive media streaming. Detailedinformation for acquisition of segments configuring content in adaptivemedia streaming may be a media presentation description (MPD).

In another embodiment, the information for providing the broadcastservice may be service information of a path for acquiring componentdata configuring content in a broadcast service. The component data maybe an entity configuring a broadcast service or content. At this time,the information on the path for acquiring the component data may beidentification information of a physical layer pipe delivering componentdata. The layered transport protocol packet may include a physical layerpipe delivered through a physical layer. A plurality of physical layerpipes may be present. Accordingly, it is necessary to distinguish aphysical layer pipe including component data to be acquired from thephysical layer pipes.

In another embodiment, the information for providing the broadcastservice may be service information for a signaling message for anapplication used in the broadcast service. At this time, the serviceinformation for the signaling message for the application may be atleast one of identifier information of a broadcaster for transmittingthe application, a source IP address of an Internet protocol datagramincluding the application, a destination IP address of the Internetprotocol datagram including the application, a port number of a userdatagram protocol (UDP) of the Internet protocol datagram including theapplication, identifier information of a transport session fortransmitting the application and identifier information of a packet fortransmitting the application.

In another embodiment, the information for providing the broadcastservice may be service information for a signaling message for a serviceused in the broadcast service. At this time, the service may be onecontent.

In another embodiment, the information for providing the broadcastservice may be service information of a flow for delivering thecomponent of the broadcast service.

FIG. 66 is a flowchart illustrating a process of operating a broadcasttransmission device according to one embodiment of the presentinvention.

A controller of the broadcast transmission device inserts informationfor providing a broadcast service into a service signaling message(S201). In one embodiment, the controller of the broadcast transmissiondevice may insert the information for providing the broadcast serviceinto the service signaling message in XML format. In another embodiment,the controller of the broadcast transmission device may insert theinformation for providing the broadcast service into the servicesignaling message in binary format.

The controller of the broadcast transmission device packetizes theservice signaling message, into which the information for providing thebroadcast service is inserted, into a transport protocol packet (S203).At this time, the transport protocol may be any one of a session basedtransport protocol (ALC/LCT or FLUTE) and a packet based transportprotocol (MPEG-2 TS or MMT).

A transmission unit of the broadcast transmission device transmits thetransport protocol packet, into which the service signaling message ispacketized, to a broadcast reception device in a specific transport mode(S205).

In one embodiment, the information for providing the broadcast servicemay be service information for a timebase including metadata on atimeline which is a series of time information for content.

In another embodiment, the information for providing the broadcastservice may be service information of detailed information foracquisition of segments configuring content in adaptive media streaming.Detailed information for acquisition of segments configuring content inadaptive media streaming may be a media presentation description (MPD).

In another embodiment, the information for providing the broadcastservice may be service information of a path for acquiring componentdata configuring content in a broadcast service. The component data maybe an entity configuring a broadcast service or content. At this time,the information on the path for acquiring the component data may beidentification information of a physical layer pipe delivering componentdata. The layered transport protocol packet may include a physical layerpipe delivered through a physical layer. A plurality of physical layerpipes may be present. Accordingly, it is necessary to distinguish aphysical layer pipe including component data to be acquired from thephysical layer pipes.

In another embodiment, the information for providing the broadcastservice may be service information for a signaling message for anapplication used in the broadcast service. At this time, the serviceinformation for the signaling message for the application may be atleast one of identifier information of a broadcaster for transmittingthe application, a source IP address of an Internet protocol datagramincluding the application, a destination IP address of the Internetprotocol datagram including the application, a port number of a userdatagram protocol (UDP) of the Internet protocol datagram including theapplication, identifier information of a transport session fortransmitting the application and identifier information of a packet fortransmitting the application.

In another embodiment, the information for providing the broadcastservice may be service information for a signaling message for a serviceused in the broadcast service. At this time, the service may be onecontent.

In another embodiment, the information for providing the broadcastservice may be service information of a flow for delivering thecomponent of the broadcast service.

One embodiment of the present invention provides a broadcasttransmission device supporting a next-generation hybrid broadcast basedon a terrestrial broadcast network and an Internet communicationnetwork, a method of operating the broadcast transmission device, abroadcast reception device and a method of operating the broadcastreception device.

In particular, one embodiment of the present invention provides abroadcast transmission device using a payload format of a servicesignaling message in a next-generation broadcast system, a method ofoperating the broadcast transmission device, a broadcast receptiondevice and a method of operating the broadcast reception device.

In particular, one embodiment of the present invention provides abroadcast transmission device using broadcast service signaling in anext-generation broadcast system, a method of operating the broadcasttransmission device, a broadcast reception device and a method ofoperating the broadcast reception device.

In particular, one embodiment of the present invention provides abroadcast transmission device using signaling of a component acquisitionpath of a broadcast service in a next-generation broadcast system, amethod of operating the broadcast transmission device, a broadcastreception device and a method of operating the broadcast receptiondevice.

In particular, one embodiment of the present invention provides abroadcast transmission device using signaling for a transmission flow ofa component of a broadcast service in a next-generation broadcastsystem, a method of operating the broadcast transmission device, abroadcast reception device and a method of operating the broadcastreception device.

The features, structures, effects, etc. of the above-describedembodiments are included in at least one embodiment of the presentinvention and are not limited to one embodiment. Further, the features,structures, effects, etc. of the above-described embodiments may beembodied by combining or modifying other embodiments by those skilled inthe art. Accordingly, such combinations or modifications may beinterpreted as being included within the scope of the present invention.

Although the invention has been described with reference to theexemplary embodiments, those skilled in the art will appreciate thatvarious modifications and variations can be made in the presentinvention without departing from the spirit or scope of the inventiondescribed in the appended claims. For example, those skilled in the artmay use each construction described in the above embodiments incombination with each other. Accordingly, differences related to suchmodifications or applications should be interpreted as being includedwithin the scope of the present invention defined by the appendedclaims.

What is claimed is:
 1. An apparatus for transmitting a broadcast signal,the apparatus comprising: a processor to generate a plurality of IP(Internet Protocol) packets, the plurality of IP packets carryingsignaling information for listing broadcast service, a content componentfor a broadcast service and service signaling information includingformat information representing a payload format of an object; aphysical layer processor to process the plurality of IP packets tooutput the broadcast signal including data in one or more PLPs (PhysicalLayer Pipes), data in a PLP being time interleaved by a TimeInterleaving (TI) block, wherein the TI block includes a number ofForward Error Correction (FEC) blocks that is equal to a differencebetween a maximum value for the TI block and a number of virtual FECblocks; and a transmitter to transmit the broadcast signal, wherein: thesignaling information is transmitted at an IP packet level; the servicesignaling information is transmitted through transport packets includedin the IP packets, the broadcast signal further includes object flowinformation, the object flow information further includes file templateinformation, the file template information includes an identifier thatis substituted with a value corresponding to a segment number, and theobject flow information further includes content type informationrepresenting a media type of the content component carried by an objectflow.
 2. The apparatus according to claim 1, the format informationincludes a value for representing that the object represents one of afile or Hypertext Transfer Protocol (HTTP) message.
 3. The apparatusaccording to claim 1, the signaling information further includes sourceIP address information, destination IP address information and adestination user datagram protocol (UDP) port number of the transportpackets.
 4. The apparatus according to claim 1, the service signalinginformation further includes a media presentation description (MPD) andapplication information for providing application-related metadata. 5.The apparatus according to claim 1, the service signaling informationfurther includes session information including information on a LayeredCoding Transport (LCT) channel in which the content component iscarried, and the session information further includes transport sessionidentifier (TSI) for the LCT channel.
 6. A method for transmitting abroadcast signal by a broadcast transmission device, the methodcomprising: generating a plurality of IP (Internet Protocol) packets,the plurality of IP packets carrying signaling information for listingbroadcast service, a content component for a broadcast service, andservice signaling information including format information representinga payload format of an object; processing the plurality of IP packets tooutput the broadcast signal including data in one or more PLPs (PhysicalLayer Pipes), data in a PLP being time interleaved by a TimeInterleaving (TI) block, wherein the TI block includes a number ofForward Error Correction (FEC) blocks that is equal to a differencebetween a maximum value for the TI block and a number of virtual FECblocks; and transmitting the broadcast signal including time interleaveddata, wherein: the signaling information is transmitted at an IP packetlevel; the service signaling information is transmitted throughtransport packets included in the IP packets, the broadcast signalfurther includes object flow information, the object flow informationfurther includes file template information, the file templateinformation includes an identifier that is substituted with a valuecorresponding to a segment number, and the object flow informationfurther includes content type information representing a media type ofthe content component carried by an object flow.
 7. An apparatus forreceiving a broadcast signal, the apparatus comprising: a receiver toreceive the broadcast signal including data that is time interleaved bya Time Interleaving (TI) block, wherein the TI block includes a numberof Forward Error Correction (FEC) blocks that is equal to a differencebetween a maximum value for the TI block and a number of virtual FECblocks; a physical layer processor to process the received broadcastsignal to output a plurality of IP (Internet Protocol) packets, theplurality of IP packets carrying signaling information for listingbroadcast service, a content component for a broadcast service andservice signaling information including format information representinga payload format of an object; and a controller to: parse the signalinginformation, service signaling information, and obtain the contentcomponent based on the service signaling information, wherein: thesignaling information is transmitted at an IP packet level; the servicesignaling information is transmitted through transport packets includedin the IP packets, the broadcast signal further includes object flowinformation, the object flow information further includes file templateinformation, the file template information includes an identifier thatis substituted with a value corresponding to a segment number, and theobject flow information further includes content type informationrepresenting a media type of the content component carried by an objectflow.
 8. A method for receiving a broadcast signal by a broadcastreception device, the method comprising: receiving the broadcast signalincluding data that is time interleaved by a Time Interleaving (TI)block, wherein the TI block includes a number of Forward ErrorCorrection (FEC) blocks that is equal to a difference between a maximumvalue for the TI block and a number of virtual FEC blocks; processingthe received broadcast signal to output a plurality of IP (InternetProtocol) packets, the plurality of IP packets carrying signalinginformation for listing broadcast service, a content component for abroadcast service and the service signaling information including formatinformation representing a payload format of an object; parsing thesignaling information, the service signaling information; and obtainingthe content component based on the service signaling information,wherein: the signaling information is transmitted at an IP packet level;the service signaling information is transmitted through transportpackets included in the IP packets, the broadcast signal furtherincludes object flow information, the object flow information furtherincludes file template information, the file template informationincludes an identifier that is substituted with a value corresponding toa segment number, and the object flow information further includescontent type information representing a media type of the contentcomponent carried by an object flow.